Re: [Libwpd-devel] WP6TibetanMap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, William Lachance wrote: > How does WordPerfect disambiguate this type of information? Perhaps > character set handling inside a list prefix/suffix needs a special > case? I'd really prefer to keep Tibetan character support in libwpd: > taking it out seems like a step backwards. Will have to investigate a bit more even maybe if there is time, improve our list/para style handling. I don't want to remove it for sure, just sometimes we are in font-dependent zone that is quite different from the unicode universal approach nowadays applications take. I would expect the charset 12 be something like char n° XYZ from the index of the font used. But, as I said, will have to investigate more. Cheers F. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGlpABu9a1imXPdA8RAhNfAJkBxKWAMqCQAjJhDhU9yTTdiRLXlACeN+V2 CowO5mjqvjEK/3HnlKH4pFc= =4Sbq -END PGP SIGNATURE- - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Libwpd-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libwpd-devel
Re: [Libwpd-devel] WP6TibetanMap
On 7/11/07, Fridrich Strba <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello, good people, I wanted just to ask some information about the > WP6TibetanMap. It is true that it makes the M*.wpd document look nice, > but I have quite a problem with what we do concerning this map because > the charset 12 is specified as user defined, and as we go now, we are > conveting always the characters from this charset as being tibetan. This > is specially wrong when this kind of characters is appearing as a list > numbering prefix/suffix. I almost feel like removing this map, but ... > > Please, advise How does WordPerfect disambiguate this type of information? Perhaps character set handling inside a list prefix/suffix needs a special case? I'd really prefer to keep Tibetan character support in libwpd: taking it out seems like a step backwards. -- William Lachance [EMAIL PROTECTED] - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Libwpd-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libwpd-devel
[Libwpd-devel] WP6TibetanMap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, good people, I wanted just to ask some information about the WP6TibetanMap. It is true that it makes the M*.wpd document look nice, but I have quite a problem with what we do concerning this map because the charset 12 is specified as user defined, and as we go now, we are conveting always the characters from this charset as being tibetan. This is specially wrong when this kind of characters is appearing as a list numbering prefix/suffix. I almost feel like removing this map, but ... Please, advise Cheers Fridrich -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGlVGpu9a1imXPdA8RAjUzAJ9cbCiPDEBVUHQs7jP49wwkMjVR/ACdFvmK ZYmYtdHvmwQCwsPYjUKDb1A= =ibRD -END PGP SIGNATURE- - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Libwpd-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libwpd-devel
