Re: msgmerge problem

2006-06-22 Thread Fernando Apesteguía
Sorry, but just to be clear:If one of my translators send me a file specifying that he used an  ISO-XXX-X encoding, what should I do? Convert to UTF-8 and set charset=UTF-8 or keep the file intact and set charset=ISO-XXX-X?
What is the preferred behaviour for a GNOME application?And another question so I don't send two mails this night :)How does gtk and glib functions behave with enconding changes? Will be string sizes affected? Should I resize my buffers? I ask this because I make a extensive use of strings and buffers to perform some parsing operations.
Thanks in advanceOn 6/19/06, Danilo Segan [EMAIL PROTECTED] wrote:
Hi Fernando,У пон, 19. 06 2006. у 18:30 +0200, Fernando Apesteguía пише: You have made me really happy! :) That worked. Just a follow up question: The enconding conversion changed some characters ( 
e.g. the last vocal now appers to be a c instead of a extrange e) is this normal?Well, Croatian uses only č, ć, đ, and ž (these are not accented c, d orz, but different letters), so it was easy for me to notice the problem
(I am Serbian, and Serbian is quite alike, if not the same as Croatian).And I know that Croatian on free software systems would probably beusing ISO-8859-2 (other than UTF-8; this is also known as Latin-2).On
Windows, it would use CP1250. And what to do if I face the same problem again? Should I change the encoding in the file's header or should I reencode with iconv? What is the difference?
You *must* (and I repeat, *must*) ask the translator who submitted atranslation in which encoding was it in — file will likely pass check ifyou convert from any 8-bit ISO-8859 encoding (either using iconv of
header field), since they all cover almost same 8-bit space.I felt safe in recommending ISO-8859-2 only because I am very wellfamiliar with what would Croatian need. :)Cheers,Danilo

___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: msgmerge problem

2006-06-22 Thread Christian Rose
On 6/22/06, Fernando Apesteguía [EMAIL PROTECTED] wrote:
 Sorry, but just to be clear:

 If one of my translators send me a file specifying that he used an ISO-XXX-X
 encoding, what should I do? Convert to UTF-8 and set charset=UTF-8 or keep
 the file intact and set charset=ISO-XXX-X?

The best thing to do would be to ask the translators to convert their
po files to UTF-8 themselves, since they are the best ones to verify
that their accented characters/script indeed are still correct when
converted.

If some translator for some reason cannot convert to UTF-8 themselves,
then of course the second best thing is for you to convert the file
for them.

You can use 'msgconv' for converting to UTF-8 (if the original
encoding information in the po header is correct) or 'iconv' (if the
encoding information in the po header is incorrect).


 What is the preferred behaviour for a GNOME application?

For any GTK+ 2 application, the preferred encoding is UTF-8.

In fact, we actually require all po files to be encoded in UTF-8 in
the GNOME Translation Project.


Christian
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


msgmerge problem

2006-06-19 Thread Fernando Apesteguía
This is the output of the Makefile:

$ make
file=./`echo hr | sed 's,.*/,,'`.gmo \
  rm -f $file  /usr/bin/msgfmt --statistics -o $file hr.po
hr.po:29:16: sucesión de multibyte inválida
hr.po:53:14: sucesión de multibyte inválida
hr.po:89:16: sucesión de multibyte inválida
hr.po:93:11: sucesión de multibyte inválida
hr.po:97:21: sucesión de multibyte inválida
hr.po:121:13: sucesión de multibyte inválida
hr.po:161:21: sucesión de multibyte inválida
hr.po:165:12: sucesión de multibyte inválida
hr.po:165:19: sucesión de multibyte inválida
hr.po:169:10: sucesión de multibyte inválida
hr.po:173:12: sucesión de multibyte inválida
hr.po:177:17: sucesión de multibyte inválida
hr.po:197:15: sucesión de multibyte inválida
hr.po:201:23: sucesión de multibyte inválida
hr.po:205:16: sucesión de multibyte inválida
hr.po:221:18: sucesión de multibyte inválida
hr.po:237:18: sucesión de multibyte inválida
hr.po:277:10: sucesión de multibyte inválida
hr.po:301:13: sucesión de multibyte inválida
hr.po:313:30: sucesión de multibyte inválida
/usr/bin/msgfmt: demasiados errores, programa interrumpido
make: *** [hr.gmo] Error 1

and this are some of the lines that throw errors (I don't copy the entire file because it is 390 lines long):

#: src/interface.c:340
msgid Vendor
msgstr Prodavaè

#: src/interface.c:382
msgid Cache
msgstr Priruèna memorija

#: src/interface.c:693
msgid Cached
msgstr U priruènoj memoriji

And the file's header is as follows:

# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR [EMAIL PROTECTED], YEAR.
#
#, fuzzy
msgid 
msgstr 
Project-Id-Version: PACKAGE VERSION\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2006-05-09 23:08+0200\n
PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n
Last-Translator: FULL NAME [EMAIL PROTECTED]\n
Language-Team: LANGUAGE [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n

Until now, we only had english and spanish translations and this is our
first attempt to add more languages (croatian,russian, etc...), so we
are a bit lost.

Any ideas?

Thanks in advance (and sorry for this long post)-- Forwarded message --From: Tomas Kuliavas 
[EMAIL PROTECTED]Date: Jun 18, 2006 7:29 PMSubject: Re: msgmerge problemTo: gnome-i18n@gnome.org Hi list, I still have the same problem that I reported a few days ago. I can't
 integrate my Croatinan .po file into my project. I'm using msgmerge and msgfmt from gettext-tools 0.14.1 Here, the es.po and eu.po are processed without problems. The .gmo files are created as expected. However the Croatian file fails at msgmerge
 throwing a lot of invalid multibyte sequence. The file's header contains these lines: Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n
 I downloaded and successfully compiled gaim and I looked for differences between it's .po files and the mine ones... but the charset and enconding are the same. My croatian translator sent the file compressed as someone recommend to
 me. I don't know what more I can do... if you want I can post the entire .po file or the complete header as you want... Can you help me please? PS: I explored another possibility but I'm not sure about that: Are
 msgmerge and msgfmt influenced by my locale configuration? Maybe my system is not properly configured?Show files used with msgmerge command or check lines numbers that aredisplayed in msgmerge warnings.
--Tomas___gnome-i18n mailing listgnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: msgmerge problem

2006-06-19 Thread Danilo Segan
Hi Fernando,

У пон, 19. 06 2006. у 14:26 +0200, Fernando Apesteguía пише:
 #: src/interface.c:340
 msgid Vendor
 msgstr Prodavaè

File is most likely encoded as ISO-8859-2.  Try passing it through iconv
first:

 $ iconv -f ISO-8859-2 -t UTF-8 hr.po hr2.po  mv hr2.po hr.po

Or, simply enter charset=ISO-8859-2 in the header field (though, I'd
recommend using UTF-8 for all languages in Gtk+-based programs).

Cheers,
Danilo


___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: msgmerge problem

2006-06-19 Thread Fernando Apesteguía
On 6/19/06, Danilo Segan [EMAIL PROTECTED] wrote:
Hi Fernando,У пон, 19. 06 2006. у 14:26 +0200, Fernando Apesteguía пише: #: src/interface.c:340 msgid Vendor msgstr ProdavaèFile is most likely encoded as ISO-8859-2.Try passing it through iconv
first: $ iconv -f ISO-8859-2 -t UTF-8 hr.po hr2.po  mv hr2.po hr.poYou have made me really happy! :)That worked. Just a follow up question: The enconding conversion changed some characters (
e.g. the last vocal now appers to be a c instead of a extrange e) is this normal?And what to do if I face the same problem again? Should I change the encoding in the file's header or should I reencode with iconv? What is the difference?
Many thanks also to Christian!Or, simply enter charset=ISO-8859-2 in the header field (though, I'd
recommend using UTF-8 for all languages in Gtk+-based programs).Cheers,Danilo
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: msgmerge problem

2006-06-19 Thread Danilo Segan
Hi Fernando,

У пон, 19. 06 2006. у 18:30 +0200, Fernando Apesteguía пише:

 You have made me really happy! :)
 That worked. Just a follow up question: The enconding conversion
 changed some characters ( e.g. the last vocal now appers to be a c
 instead of a extrange e) is this normal?

Well, Croatian uses only č, ć, đ, and ž (these are not accented c, d or
z, but different letters), so it was easy for me to notice the problem
(I am Serbian, and Serbian is quite alike, if not the same as Croatian).

And I know that Croatian on free software systems would probably be
using ISO-8859-2 (other than UTF-8; this is also known as Latin-2).  On
Windows, it would use CP1250.

 And what to do if I face the same problem again? Should I change the
 encoding in the file's header or should I reencode with iconv? What is
 the difference? 

You *must* (and I repeat, *must*) ask the translator who submitted a
translation in which encoding was it in — file will likely pass check if
you convert from any 8-bit ISO-8859 encoding (either using iconv of
header field), since they all cover almost same 8-bit space.

I felt safe in recommending ISO-8859-2 only because I am very well
familiar with what would Croatian need. :)

Cheers,
Danilo



___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: msgmerge problem

2006-06-19 Thread Tomas Kuliavas
Text is not in utf-8. According to email headers it is in iso-8859-1.
Please don't paste 8bit translation texts in message body. Attach them. If
you paste text inline, only your mailer and your deity knows what is in
original.


you have broken file header.

# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR [EMAIL PROTECTED], YEAR.
#
#, fuzzy
msgid 
msgstr 
Project-Id-Version: PACKAGE VERSION\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2006-05-09 23:08+0200\n
PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n
Last-Translator: FULL NAME [EMAIL PROTECTED]\n
Language-Team: LANGUAGE [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n


don't leave it as is. Fill comments and msgstr lines. Remove fuzzy mark.
If you don't do that, your translation does not pass msgfmt -c tests.


if you want to test your translation, test it with 'msgfmt -v -c -o
/dev/null hr.po' command. You can also add '--check-accelerators=_' for
Gnome translations.

 This is the output of the Makefile:

 $ make
 file=./`echo hr | sed 's,.*/,,'`.gmo \
rm -f $file  /usr/bin/msgfmt --statistics -o $file hr.po
 hr.po:29:16: sucesión de multibyte inválida
 hr.po:53:14: sucesión de multibyte inválida
 hr.po:89:16: sucesión de multibyte inválida
 hr.po:93:11: sucesión de multibyte inválida
 hr.po:97:21: sucesión de multibyte inválida
 hr.po:121:13: sucesión de multibyte inválida
 hr.po:161:21: sucesión de multibyte inválida
 hr.po:165:12: sucesión de multibyte inválida
 hr.po:165:19: sucesión de multibyte inválida
 hr.po:169:10: sucesión de multibyte inválida
 hr.po:173:12: sucesión de multibyte inválida
 hr.po:177:17: sucesión de multibyte inválida
 hr.po:197:15: sucesión de multibyte inválida
 hr.po:201:23: sucesión de multibyte inválida
 hr.po:205:16: sucesión de multibyte inválida
 hr.po:221:18: sucesión de multibyte inválida
 hr.po:237:18: sucesión de multibyte inválida
 hr.po:277:10: sucesión de multibyte inválida
 hr.po:301:13: sucesión de multibyte inválida
 hr.po:313:30: sucesión de multibyte inválida
 /usr/bin/msgfmt: demasiados errores, programa interrumpido
 make: *** [hr.gmo] Error 1

 and this are some of the lines that throw errors (I don't copy the entire
 file because it is 390 lines long):

 #: src/interface.c:340
 msgid Vendor
 msgstr Prodavaè

 #: src/interface.c:382
 msgid Cache
 msgstr Priruèna memorija

 #: src/interface.c:693
 msgid Cached
 msgstr U priruènoj memoriji

 And the file's header is as follows:

 # SOME DESCRIPTIVE TITLE.
 # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
 # This file is distributed under the same license as the PACKAGE package.
 # FIRST AUTHOR [EMAIL PROTECTED], YEAR.
 #
 #, fuzzy
 msgid 
 msgstr 
 Project-Id-Version: PACKAGE VERSION\n
 Report-Msgid-Bugs-To: \n
 POT-Creation-Date: 2006-05-09 23:08+0200\n
 PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n
 Last-Translator: FULL NAME [EMAIL PROTECTED]\n
 Language-Team: LANGUAGE [EMAIL PROTECTED]\n
 MIME-Version: 1.0\n
 Content-Type: text/plain; charset=UTF-8\n
 Content-Transfer-Encoding: 8bit\n

 Until now, we only had english and spanish translations and this is our
 first attempt to add more languages (croatian,russian, etc...), so we are
 a
 bit lost.

 Any ideas?

 Thanks in advance (and sorry for this long post)

 -- Forwarded message --
 From: Tomas Kuliavas [EMAIL PROTECTED]
 Date: Jun 18, 2006 7:29 PM
 Subject: Re: msgmerge problem
 To: gnome-i18n@gnome.org

 Hi list,

 I still have the same problem that I reported a few days ago. I can't
 integrate my Croatinan .po file into my project. I'm using msgmerge and
 msgfmt from gettext-tools 0.14.1

 Here, the es.po and eu.po are processed without problems. The .gmo files
 are created as expected. However the Croatian file fails at msgmerge
 throwing a lot of invalid multibyte sequence.
 The file's header contains these lines:

 Content-Type: text/plain; charset=UTF-8\n
 Content-Transfer-Encoding: 8bit\n

 I downloaded and successfully compiled gaim and I looked for differences
 between it's .po files and the mine ones... but the charset and
 enconding
 are the same.
 My croatian translator sent the file compressed as someone recommend to
 me.

 I don't know what more I can do... if you want I can post the entire .po
 file or the complete header as you want...

 Can you help me please?

 PS: I explored another possibility but I'm not sure about that: Are
 msgmerge
 and msgfmt influenced by my locale configuration? Maybe my system is not
 properly configured?

 Show files used with msgmerge command or check lines numbers that are
 displayed in msgmerge warnings.

 --
 Tomas
 ___
 gnome-i18n mailing list
 gnome-i18n@gnome.org
 http://mail.gnome.org/mailman/listinfo/gnome-i18n
 ___
 gnome-i18n mailing list
 gnome

msgmerge problem

2006-06-18 Thread Fernando Apesteguía
Hi list,

I still have the same problem that I reported a few days ago. I can't
integrate my Croatinan .po file into my project. I'm using msgmerge and
msgfmt from gettext-tools 0.14.1

Here, the es.po and eu.po are processed without problems. The .gmo
files are created as expected. However the Croatian file fails at
msgmerge throwing a lot of invalid multibyte sequence.
The file's header contains these lines:

Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n

I downloaded and successfully compiled gaim and I looked for
differences between it's .po files and the mine ones... but the charset
and enconding are the same.
My croatian translator sent the file compressed as someone recommend to me.

I don't know what more I can do... if you want I can post the entire .po file or the complete header as you want... 

Can you help me please?

PS: I explored another possibility but I'm not sure about that: Are
msgmerge and msgfmt influenced by my locale configuration? Maybe my
system is not properly configured?

Best regards and thanks in advance
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: msgmerge problem

2006-06-18 Thread Tomas Kuliavas
 Hi list,

 I still have the same problem that I reported a few days ago. I can't
 integrate my Croatinan .po file into my project. I'm using msgmerge and
 msgfmt from gettext-tools 0.14.1

 Here, the es.po and eu.po are processed without problems. The .gmo files
 are created as expected. However the Croatian file fails at msgmerge
 throwing a lot of invalid multibyte sequence.
 The file's header contains these lines:

 Content-Type: text/plain; charset=UTF-8\n
 Content-Transfer-Encoding: 8bit\n

 I downloaded and successfully compiled gaim and I looked for differences
 between it's .po files and the mine ones... but the charset and enconding
 are the same.
 My croatian translator sent the file compressed as someone recommend to
 me.

 I don't know what more I can do... if you want I can post the entire .po
 file or the complete header as you want...

 Can you help me please?

 PS: I explored another possibility but I'm not sure about that: Are
 msgmerge
 and msgfmt influenced by my locale configuration? Maybe my system is not
 properly configured?

Show files used with msgmerge command or check lines numbers that are
displayed in msgmerge warnings.

-- 
Tomas
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n