Re: Patch: Fix for Bug 1164, 2nd try


Subject: Re: Patch: Fix for Bug 1164, 2nd try
From: Vlad Harchev (hvv@hippo.ru)
Date: Tue May 22 2001 - 04:59:48 CDT


On Tue, 22 May 2001, ha shao wrote:

> On Tue, May 22, 2001 at 12:47:09PM +0500, hvv@hippo.ru wrote:
> > On Tue, 22 May 2001, ha shao wrote:
> .....
> > > \kerning0\cf0\viewkind1\paperw12240\paperh15840\margl1440\margr1440\widowctl
> > > \sectd\sbknone\colsx360\headery0\footery0
> > > \pard{\f0 \'b3\'d4\'c1\'cb\'c2\'f0}}
> >
> > Is it correct RTF (seems so)?
> >
>
> Yes, it is correct.
>
> > Andrew's RTF looks different from yours because Andrew is running Win2k - it
> > seems XAP_EncodingManager.is_cjk_locale() returns 0 under Win2k and 1 (as
> > expected) under unix. Andrew, coduld you correct this (make is_cjk_locale()
> > returning proper value)?
>
> If the \uxxxx output is correct (that other wp can load it with no

 Wordpad from Win95 won't load it (\uxxx form). May be from win98
too. There may be other primitive editors that won't load it.
 So I think it would be safer not to use \uxxxx form for maximum
compatibility. So correctly working is_cjk_locale() seems to be needed.

> problem), maybe the is_cjk_locale is not needed? Sorry, I forget the
> reason to have that in the place. We must have some reason...
> Maybe for export to the 'rtf for old application' format?

 is_cjk_locale is widely used internally on unix - for printing, drawing etc.
 As for 'rtf for old apps' - its output doesn't differ from usual RTF
exporter's for multibyte locales. Only for singlebyte ones (it's for
StarOffice 5.2 that doesn't parse RTF correctly).

> --
> Best regard
> hashao
>

 Best regards,
  -Vlad



This archive was generated by hypermail 2b25 : Sat May 26 2001 - 03:51:06 CDT