Re: About the zh_CN.GB2312 locale

[Zhang Lin-bo <zlb lsec cc ac cn>]

> Uh. Now I'm puzzled. I guess it'll take being more defensive on the loop you
> have highlighted in your previous message. Please still forward the .po
> changes to the zh_CN.po maintainer, unless the Postscript font names are the
> what the contents of the translated strings were.

I have sent the suggested modifications to lark@linux.net.cn

>
> When you mean "Western", do you mean latin1, latin0 or do you mean ASCII ?

Sorry I meant ASCII.

>
> I'm afraid outside Ghostscript, UTF-8 is something undefined.
> However, it would be very nice if we could work out something using
> the re-encoding and your existing fonts (I'll need samples of working and
> non-working files, relevant fonts, and a PNG screen shot of expected
> results).

Attached is a sample diagram (zh_CN.dia, zh_CN.png,
zh_CN-working.eps created by my modified Dia,
and zh_CN-nonworking.eps created by the original Dia).

The Chinese fonts needed are in the ttfonts-zh_CN-2.11-21 package,
and ghostscript resource files in ghostscript-6.52-8, both
packages are from rh7.3. After installing the packages, you
need to create the UTF-8 encoded fonts (*-UniGB-UTF8-H) by:

	cd /usr/share/ghostscript/Resource
	./ag1.sh install BousungEG-Light-GB
	./ag1.sh install GBZenKai-Medium

>
> Until you can show me a spec from Adobe saying that UTF-8 is fine in
> Postscript, the answer is 'no'. I won't let dia generate
> Ghostscript-specific code. However, I do want to make dia work for all
> locales using all scripts; I would prefer the map-switching code to be made
> working for zh_CN (Akira TAGOH made a lot of work in this area during the
> spring, and it was supposed to work for all CJK languages)

You may be right. I don't know much about issues concerning portability
of PS files. I have looked at the PS files created by other programs,
for example, AbiWord uses GB-EUC encoding (I can modify Dia to work this
way), while mozilla seems to directly use the CID fonts.

>
> Specifically, I don't understand why the \uni1234 notation doesn't work in
> your case -- it definitely should.

I think that the problem is due to lack of corresponding font files
which support unicode encoding (none of the font files created by ag1.sh
are usable, and I don't know how to create the required one by myself).

The problem may be simple for someone who's familiar with PS fonts
and encodings. But I just don't know how to do it.

>
> A couple test cases would be worth trying:
>         * a diagram with a few symbols (less than 256)
>         * a diagram with a lot of symbols (more than 256)
>
> You may want however to test whether enabling only the first half of your
> patch (the lib/font.c section) and leaving the lib/ps-utf8.c code is enough
> to solve the problem ?

No. The "*-UniGB-UTF8-*" fonts only accepts UTF-8 encoding. I have tried
every font in the directory /usr/share/ghostscript/Resource/Font created
by ag1.sh, none of them works with the /uniXXXX (or /A) notation.

>
> PS: don't forget to subscribe to the list. Currently, an administrator has
> to unlock each of your posts.

Done.

I did not subscribe because I was receiving too many messages
each day, and I thought I just need to post a few questions.
Sorry for the mess.

>
>         -- Cyrille

LB

dia-sample.tar.bz2