<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.3103.1000" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2><BR>----- Original Message -----<BR>From: "Erik K.
Pedersen" <<A
href="mailto:epedersen@stny.rr.com">epedersen@stny.rr.com</A>><BR>To: <<A
href="mailto:rfunken@kdevelop.de">rfunken@kdevelop.de</A>><BR>Sent: Monday,
January 22, 2001 4:47 AM<BR>Subject: Non-ascii characters in
kdevelop.pot<BR><BR><BR>> The non-ascii characters are the following
6<BR>><BR>> Switches to the KDE 2 Developer´s Guide
Handbook<BR>>
^<BR>> In the path you´ve
given<BR>>
^<BR>> and which are applied---every thing interesting
about how make
decides<BR>>
^<BR>><BR>> processing. This may be use ful
for tracking down errors
from<BR>>
^<BR>> doesn´t exist
anymore.<BR>> ^<BR>>
o´clock<BR>> ^<BR>><BR>> I hope I have solved the other problem.
I noticed there is the same<BR>problem<BR>> in say the Norwegian translation,
it does not compile<BR>><BR>> msgfmt -v kdevelop.po<BR>> field
`Project-Id-Version' still has initial default value<BR>> kdevelop.po:3683:
parse error<BR>> kdevelop.po:7753: parse error<BR>> kdevelop.po:7759:
parse error<BR>> kdevelop.po:7765: parse error<BR>> kdevelop.po:7771:
parse error<BR>> kdevelop.po:7787: parse error<BR>> kdevelop.po:7793:
parse error<BR>> kdevelop.po:7810: parse error<BR>> found 9 fatal
errors<BR>><BR>> that is something that happened once in the mergerocess
and persists until<BR>> the translator fixes
kdevelop.po<BR><BR>Hi,<BR><BR>The ASCII codes for the characters are, in order
of appearance : 6F, 76, 74,<BR>72, 65, B4. As far as I know these are all in
standard range except for B4<BR>which is extended ASCII. OK, it should be 27
instead of B4 (wrong key used<BR>by the programmer, should be ' instead of`´)
but I can't think of any editor<BR>or tool that isn't capable of handling 16
bit. The ycp error was caused by<BR>data loss during transmission, because I
attached the file to an e-mail sent<BR>it to Thomas Diehl. The file I committed
yesterday should be clear. I told<BR>Thomas some weeks ago, that the non ASCII
codes have to cleared in the po's,<BR>not in the pot and are the the result of
us using ISO in the KDE 1 versions.<BR>I have no problems creating po's simply
using "make package messages" (Yes,<BR>it's as difficult as that). No recode or
so needed. Just use kbabel to edit<BR>the po files and save as utf-8.<BR><BR>I
told Thomas and Ralf Nolden yesterday and I repeat here that it's sad
but<BR>true, but everything went fine, when we did the whole job ourselves.
I<BR>really have a lot of better things to do, than to update libs and things
the<BR>whole weekend only to discuss about ASCII Codes. It was fun until
the<BR>release of 1.3 but now that i18 stuff has turned out to be a pain in
the<BR>arse. I said I'd do the po's for 1.4 and so I'll do, but after that I
won't<BR>be available for the i18n stuff anymore. Maybe I'll find the time
do<BR>contribute something different in the future, but to be honest, I'm so
short<BR>on time now, I can't imagine how to do it.<BR>Anyway, I'd like to thank
you guys for this really great time. It was both,<BR>a pleasure and an honour to
play in your team. I regret I didn't get to know<BR>more of you personally, John
: Sorry, I still didn't make it for dinner, but<BR>maybe the invitation still
stands? :-)).<BR><BR><BR>Regards,<BR><BR>Ralf<BR></FONT></DIV></BODY></HTML>