Jason Aiken wrote: > > Is anyone aware of the difficulties involved in supporting katakana? What hoops of fire must one jump through?
We've been using Epic 4.2.1 with all the Asian languages Arbortext claims to support and it works fine, although we haven't stressed it heavily yet (but will over the next couple of weeks). The only thing special I did was install all the national language fonts under Win2K (through the regional options). I can work with documents in both UTF-8 and UTF-16 encodings no prob. I also found that Textpad 4.5+ useful for looking at UTF-16 documents (www.textpad.com).
We aren't doing any Asian authoring ourselves, just processing docs we get from a supplier, so I can't speak to problems with actually keyboarding Asian data in Epic.
We use Adept Publisher 8.1 Global (this is the highest version from Arbortext products that support double-byte Unicode char) under Windoze 2000 with Japanese locale setting (officialy you have to use NT 4 Japanese but we have not encountered any problem with W2000).
XML files are UTF-8 encoded.
Only problem: we must use specific char entities along with a specific font to print some unsupported kanjis (gaijis).
If you do not need to publish you can use Epic 4.2.1 under Windoze 2000 with Japanese locale setting.
HTH and feel free to ask further question.
> Is anyone aware of the difficulties involved in supporting katakana? What > hoops of fire must one jump through? > > Just curious, > Jason Aiken > Acolyte > Adeptus Mechanicus >
We also use Adept Global 8.1 for producing printed output from SGML and it has worked fine for Japanese, Korean, and simplified/traditional Chinese. We're doing it on a Win/NT platform.
Is anyone authoring SGML/XML using Epic/Adept and having to deal with a translation vendor that uses TRADOS? I'm curious about problems TRADOS vendors have when delivered SGML/XML. What other translation tools are out there?
we encountered some problems with Trados Version 3. This Version doesn't support entities and has some problems with the PUBLIC identifier. At the moment it looks like we don't have any problem with Version 5.
Another Translation Tool is STAR (www.star-transit.com)