Hinweis: Es scheint, Ihr Browser unterstützt nicht alle Web-Standards, und deshalb sehen Sie diesen Hinweis und das Layout nur in Auszügen. Bitte verwenden Sie einen aktuelleren Browser.

CAP Studio · FrameScript · /fminit/ · WWP Info [de|en]

All languages on a single page

Thanks to the Unicode standard it is possible using WebWorks Publisher to create an HTML page containing characters from all fonts that can be used with FrameMaker.

See for yourself!

Does your conversion setup handle all characters?

Does your current conversion setup handle all available FrameMaker characters correctly?

Check it using the test document FM_Character_Sets_Windows.mif and compare the conversion result with a print-out of that document.

Free download: FM_Character_Sets_Windows.mif (zipped: 50kB)

By the way: A file similar to this used to be part of the FrameMaker installation until version 5.5.6. Later versions contained that file in PDF format only.

Note regarding WWP 7 and 2003

WebWorks Publisher Professional 7 and 2003 contain character mappings for the codepages 1250, 1251, 1253, 1254, and 1257, like you need them for MS HTML Help 1.x. Unfortunately the Euro sign is not supported by these mappings. And those mappings do not support the Unicode standard UTF-8, i.e. you can only use characters from a single codepage in a single WebWorks Publisher project. If you have a Russian project, you cannot use any accented characters from other European languages like á, é, è, Ä, Ö, or Ü.

Unicode Support

Media publication for all countries of the European Union and others is a challenge for desktop publishing tools. Adobe FrameMaker is not making life easy for its users, because the product does not support the Unicode standard. But it features other productivity advantages which make it the first choice in the field of technical communication.

All challenges meeting FrameMaker, are of course challenges for WebWorks Publisher too. But the first part of a solution must be found for FrameMaker.

The FrameMaker solution

Just a few short notes on that topic. For programs like FrameMaker, which do not support the Unicode standard, Windows implements a method using codepages. The Arial font for instance contains characters (glyphs) for all Latin, Cyrillic and Greek alphabets. But FrameMaker "sees" only the characters of the western codepage Windows-1252.

Using special entries in the Windows Registry (e.g. using WGL AssistantNeues Fenster) it is possible to create so-called virtual fonts, which contain the characters of another codepage. For Arial this could be:

  • Arial CE: Codepage Windows-1250 for Czech (cz), Hungarian (hu), Polish (pl), Romanian (ro), Slovak (sk), Slovenian (sl)
  • Arial CYR: Codepage Windows-1251 for Belarusian (be), Bulgarian (bg), Russian (ru), Ukrainian (uk)
  • Arial Greek: Codepage Windows-1253 for Greek (el)
  • Arial TUR: Codepage Windows-1254 for Turkish (tr)
  • Arial Baltic: Codepage Windows-1257 for Estonian (et), Lithuanian (lt), Latvian (lv)

FrameMaker treats those fonts like any other codepage Windows-1252 font. That is, the product does not "know" it is a font with other glyphs. And consequently WebWorks Publisher doesn't "know" that either!

The WebWorks Publisher solution

Using WebWorks Publisher you can select a separate character mapping for every font. So the tools are there, to give the product the necessary knowledge how to treat the special virtual fonts.

WebWorks Publisher Professional 7 and WebWorks Publisher Professional 2003 contain character mappings for those codepages. But these mappings require that the generated HTML pages are encoded using the respective codepage. I.e. you can only use characters from a single codepage in a WebWorks Publisher project. If you have a Russian project, you cannot use any accented characters from other European languages like á, é, è, Ä, Ö, or Ü. Also, the Euro symbol is not handled correctly by those character mappings.

The codepage encoding is necessary for MS HTML Help 1.x. This format does not allow the usage of characters from different language families; strictly speaking this is only true for the table of contents and the index, but those cannot be handled separately by WebWorks Publisher.

Most important is creating output files according to the Unicode standard UTF-8, like WebWorks Publisher allows this for western characters.

My offer

I deliver complete and correct Character Mappings to be used for codepage encoding and Unicode UTF-8 encoding!

Available add-ons

¹) Hold the mouse cursor on top of the abbreviation to see the full language name.

*) see the note regarding WebWorks Publisher Professional 7 and WebWorks Publisher Professional 2003 in the right column.

deen

Quadralay and WebWorks are trademarks of Quadralay Corporation, Austin, U.S.A.
Adobe and FrameMaker are trademarks of Adobe Corporation.
http://wwp.cap-studio.de/en/unicode.html
Last changed: 01.02.2005 20:31:28
© 2008 . All rights reserved.
Created using SchemaText 3.00 at 11.04.2008 16:03:05
Top of Page