On Thu, 26 Apr 2001, Geoffrey Lee wrote:

Behaviour changed between gettext <= 0.10.35 and gettext > 0.10.35 .
Originally double backslash is needed. However after upgrading gettext,
double backslash will give fatal error instead. No need to use double
backslash anymore :)

Abel Cheung


> On Thu, Apr 26, 2001 at 04:16:38AM +0800, R.I.P. Deaddog wrote:
> > On Tue, 24 Apr 2001, Stefan van der Eijk wrote:
> >
> > > I recompiled the packages, and re-installed them... it doesn't seem to
> > > help...
> > [snip]
> > > msgfmt -o zh_TW.Big5.mo zh_TW.Big5.po
> > > zh_TW.Big5.po:707: invalid control sequence
> > > zh_TW.Big5.po:836: invalid control sequence
> > > zh_TW.Big5.po:1286: invalid control sequence
> > > found 3 fatal errors
> >
> > It must be because of unhandled backslash in big5 encoding char. I'll take
> > a look soon........
> >
>
>
> NOt just with one but other packages as well. But paritcularly I have been
> seeing this for Chinese after the new gettext ... it seems to be more strict
> in processing .po files.
>
> > Abel Cheung
>
>


Reply via email to