Hi, doXulting, that is importing datas for "Ecole des Mines", reported a problem with extended chars like éà... I've searched previous version of Biblio.pm, because it worked. I've found that the 1.75 version, commited by slef, transforms every replaces by a single char : version 1.74 => s/\xe1\x65/è/gm ; s/\xe1\x69/ì/gm ; s/\xe1\x6f/ò/gm ; s/\xe1\x75/ù/gm ; s/\xe1\x41/À/gm ; s/\xe1\x45/È/gm ; s/\xe1\x49/Ì/gm ; s/\xe1\x4f/Ò/gm ; s/\xe1\x55/Ù/gm ; s/\xe2\x41/Á/gm ; s/\xe2\x45/É/gm ; s/\xe2\x49/Í/gm ; s/\xe2\x4f/Ó/gm ; version 1.75 => s/\xe1\x65/€/gm ; s/\xe1\x69/€/gm ; s/\xe1\x6f/€/gm ; s/\xe1\x75/€/gm ; s/\xe1\x41/€/gm ; s/\xe1\x45/€/gm ; s/\xe1\x49/€/gm ; s/\xe1\x4f/€/gm ; s/\xe1\x55/€/gm ; s/\xe2\x41/€/gm ; s/\xe2\x45/€/gm ; s/\xe2\x49/€/gm ; s/\xe2\x4f/€/gm ; s/\xe2\x55/€/gm ; s/\xe2\x59/€/gm ; I think slef has a pb with it's editor software, at least with char encoding :-). I'll rollback to normal situation, but be careful (it's the 2nd time this happends : see btw 1.54 & 1.55) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
On 2003-12-09 15:47:36 +0000 paul POULAIN <paul.poulain@free.fr> wrote:
I think slef has a pb with it's editor software, at least with char encoding
No, you seem to have a problem with your editor, but my systems show the error up. You keep putting invalid characters in Biblio.pm which make it fail for me. I think you need to either upgrade to an editor correctly supporting UTF-8, or use \xNN escape codes for characters in your local character set. Please can we avoid incompatible character sets littering the source code? -- MJR mjr@ttllp.co.uk www.ttllp.co.uk +44 (0)870 4321 9 10 Creative copyleft computing consultancy, code and articles. Latest news: Working on the 2.0 release of koha for libraries
MJ Ray a écrit :
On 2003-12-09 15:47:36 +0000 paul POULAIN <paul.poulain@free.fr> wrote:
I think slef has a pb with it's editor software, at least with char encoding
No, you seem to have a problem with your editor, but my systems show the error up. You keep putting invalid characters in Biblio.pm which make it fail for me. I think you need to either upgrade to an editor correctly supporting UTF-8, or use \xNN escape codes for characters in your local character set. Please can we avoid incompatible character sets littering the source code?
OK, I think I understand the problem : I use iso 8859-1, you use UTF-8. Am I right ? (I'm sure i use iso8859-1. I ask for your UTF-8 encoding) Until we swap to unicode, we should stay in iso8859-1, imho. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
On 2003-12-10 09:24:04 +0000 paul POULAIN <paul.poulain@free.fr> wrote:
Until we swap to unicode, we should stay in iso8859-1, imho.
When did that change? Last I knew, koha was not in iso8859-1, but in POSIX or C locale. Until we swap to UTF-8, we should stay as it is and use escape codes for other characters. Moving to 8859-1 now seems short-sighted to me, as it will cause problems like this one and need fixing later. -- MJR/slef My Opinion Only and possibly not of any group I know. Please http://remember.to/edit_messages on lists to be sure I read http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
participants (3)
-
MJ Ray -
MJ Ray -
paul POULAIN