Denis Barbier:
This is why I suggest to insert backslashes in MO files and not PO files.
Those backslashes will be removed when processed through WML.
The thing is that there are no backslashes, only 0x5C bytes. Those are
very different, although they might look very similar at a first
look...
On Wed, Jan 29, 2003 at 07:28:57AM +0100, Peter Karlsson wrote:
Denis Barbier:
This is why I suggest to insert backslashes in MO files and not PO files.
Those backslashes will be removed when processed through WML.
The thing is that there are no backslashes, only 0x5C bytes. Those are
Denis Barbier:
Err, ascii(7) tells me that 0x5C *is* a backslash.
Yes, but these documents aren't ASCII, so 0x5C may not or may not be a
backslash there, depending on where they are located in the file.
Could you please have a look at chinese/po/others.zh.po and tell me
what to do with
* Denis Barbier [EMAIL PROTECTED] [2003-01-29 10:32]:
On Wed, Jan 29, 2003 at 07:28:57AM +0100, Peter Karlsson wrote:
The thing is that there are no backslashes, only 0x5C bytes. Those are
very different, although they might look very similar at a first
look...
Err, ascii(7) tells me that
On Wed, Jan 29, 2003 at 11:14:56AM +0100, Peter Karlsson wrote:
Denis Barbier:
Err, ascii(7) tells me that 0x5C *is* a backslash.
Yes, but these documents aren't ASCII, so 0x5C may not or may not be a
backslash there, depending on where they are located in the file.
Ok.
Could you
Denis Barbier wrote:
Hi,
there are trouble with big5 encoding in PO files, because some
backslashes are not escaped (e.g. MailingLists/subscribe.wml
cannot be processed). Maybe fix_big5.pl should be run against
those PO files so that MO files contain escaped backslashes?
But I am not sure that
Rex Tsai wrote:
I fixed the problem and commited.
Oops, removed x5c again, I will check the wml scripts for fixed the
problem at wml compile time.
--
-Rex, geek by nature linux by choice
Denis Barbier:
there are trouble with big5 encoding in PO files, because some
backslashes are not escaped (e.g. MailingLists/subscribe.wml
cannot be processed).
Characters in the Big5 encoding may end in 0x5C byte, so the scripts
that handles it need to be aware of the locale and process the
On Tue, Jan 28, 2003 at 07:02:44AM +0100, Peter Karlsson wrote:
[...]
Maybe fix_big5.pl should be run against those PO files so that MO
files contain escaped backslashes?
If you insert extra 0x5C bytes into the stream, the text will look very
broken to a Big5 text editor.
This is why I
Hi,
there are trouble with big5 encoding in PO files, because some
backslashes are not escaped (e.g. MailingLists/subscribe.wml
cannot be processed). Maybe fix_big5.pl should be run against
those PO files so that MO files contain escaped backslashes?
But I am not sure that encoding is then still
10 matches
Mail list logo
