cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Katakana

Highlighted
Level 1

Katakana

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


Tags (2)
6 REPLIES 6

Re: Katakana

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.

Cheers,

Eliot
ISOGEN International, LLC


Re: Katakana


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.

Olivier.

> 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
>


Re: Katakana

--=====================_948912468==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

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?

Dave Hintz

Background color

--=====================_969231750==_.ALT

Background color

David,

The quick answer is:

window_set(window_id, "canvasBackground", color_name)

color_name can be a name or an RGB specification (prefixed with #)

The tricky part is ensuring that all views receive the background,
including split screens. If that becomes a problem for you, post
again.

Paul

Re: Katakana

Hi,

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)

Dirk