GNOME.org
 

[GnomeMeeting-devel-list] Re: Moving to gnome-doc-utils

Thank you Stephan and Daniel for these nice explanations and advices.
That's seems to me clear now and even it appear quite simple to do.
I'm going to do some tests whith gtranslator (I mainly use Gnome), kbabel and QT Linguist. 
Greetings,
PhL

gnomemeeting-devel-list-request gnome org a �it :


Send Gnomemeeting-devel-list mailing list submissions to
	gnomemeeting-devel-list gnome org

To subscribe or unsubscribe via the World Wide Web, visit
	http://mail.gnome.org/mailman/listinfo/gnomemeeting-devel-list
or, via email, send a message with subject or body 'help' to
	gnomemeeting-devel-list-request gnome org

You can reach the person managing the list at
	gnomemeeting-devel-list-owner gnome org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gnomemeeting-devel-list digest..."


Today's Topics:

  1. Re: Moving to gnome-doc-utils (Damien	Sandras) (Philippe Lefevre)
  2. Re: Re: Moving to gnome-doc-utils (Damien	Sandras) (Stefan Bruens)
  3. Re: Re: Moving to gnome-doc-utils (Damien	Sandras)
     (Daniel Huhardeaux)


----------------------------------------------------------------------

Message: 1
Date: Fri, 29 Jul 2005 19:21:16 +0200
From: Philippe Lefevre <ph l libertysurf fr>
Subject: [GnomeMeeting-devel-list] Re: Moving to gnome-doc-utils
	(Damien	Sandras)
To: gnomemeeting-devel-list gnome org
Message-ID: <42EA658C 3000508 libertysurf fr>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi Stephan,
I'd like just get some infos about the recent change made in translated documentation.
I did the GM french translation. To do this, I used some very low levels tools (I mean vi ;-) ) and rewrite any sentence to the translated one without any change in the docbook format.
Now, I suppose I'll have to change this way of work and it would probably be better and more 
"professional". That's great.
I had a look today on http://kvota.net/doc-l10n/by-modules.html#gnomemeeting to get some examples 
and try to understand how it works but I must say I don't see.
Could you please explain a bit the way for me to maintain gnomemeeting.xml in the future ? 
What is a po ? What is the POT file ? What are the principles now ?
May be you could email me directly to avoid polluting the devel list ? (ph_dot_l_at_libertysurf_dot_fr)
An other point : is there any way to be aware that gnomemeeting is available on 
http://kvota.net/doc-l10n....... ?

In advance, thank you for your help,
greetings,

PhL


gnomemeeting-devel-list-request gnome org a écrit :


 1. Re: Moving to gnome-doc-utils (Damien Sandras)


----------------------------------------------------------------------

Message: 1
Date: Fri, 29 Jul 2005 09:49:52 +0200
From: Damien Sandras <dsandras seconix com>
Subject: Re: [GnomeMeeting-devel-list] Moving to gnome-doc-utils
To: GnomeMeeting development mailing list
	<gnomemeeting-devel-list gnome org>, 	lurch gmx li
Message-ID: <1122623392 7734 5 camel golgoth01>
Content-Type: text/plain; charset=ISO-8859-15

Hi Stefan,

I will apply this patch next week once I've finished my work on OPAL.

That's a great patch, thanks for it !

Le jeudi 28 juillet 2005 � 23:48 +0200, Stefan Bruens a écrit :



Hi,

attached is a patch for moving to gnome-doc-utils.

What is it all about?
The strings to translate are extracted from the english gnomemeeting.xml and put into an pot. Translators can then use this to create a po with their translations commit these po's to cvs. During 'make dist' the translations are merged into the english gnomemeeting.xml, which holds the structural information, and a gnomemeeting-<lang>.xml is created, so the dist tarball holds (almost) the same files as before. 

What are the benefits?
First, the translators are used to po's, the gui translation can be used as a compendium to create a consistent translation. Second, when the documentation is changed (added/removed/changed paragraphs), only the translations for this paragraphs are marked untranslated/fuzzy, which makes tracking documentation changes much easier. Last but not least, there are translation statistics for the documentation, and who wants to be the only one not reaching 100% :-) -> more documentation translations. 

What has to be done?
* @damien
- make sure you have a recent enough gnome-common (2005-07-19) - Apply the attached patches 
	- remove the files mentioned in 'files-to-remove'
	- commit fr.po to help/fr/fr.po
* @translators
- wait for gnomemeeting to appear on http://kvota.net/doc-l10n/by-modules.html#gnomemeeting 
	- grab the pot and translate
* @packagers
	- nothing changes

Greetings,

Lurchi

_______________________________________________
Gnomemeeting-devel-list mailing list
Gnomemeeting-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/gnomemeeting-devel-list




------------------------------

Message: 2
Date: Fri, 29 Jul 2005 22:24:58 +0200
From: Stefan Bruens <lurch gmx li>
Subject: Re: [GnomeMeeting-devel-list] Re: Moving to gnome-doc-utils
	(Damien	Sandras)
To: GnomeMeeting development mailing list
	<gnomemeeting-devel-list gnome org>
Message-ID: <200507292225 05358 lurch gmx li>
Content-Type: text/plain; charset="utf-8"

Am Freitag, 29. Juli 2005 19:21 schrieb Philippe Lefevre:

Hi Stephan,

I'd like just get some infos about the recent change made in translated
documentation.

I did the GM french translation. To do this, I used some very low levels
tools (I mean vi ;-) ) and
rewrite any sentence to the translated one without any change in the
docbook format.


To this point, there are no big changes. A short snip from the french po:
--------
#: ../C/gnomemeeting.xml:64(releaseinfo) msgid "This documentation is for version 1.2 of GnomeMeeting." 
msgstr "Cette documentation est celle de GnomeMeeting version 1.2."
#: ../C/gnomemeeting.xml:69(para) msgid "User manual for the GnomeMeeting videoconferencing, IP Telephony and VoIP application" msgstr "Manuel utilisateur du logiciel de vidéoconférence, téléphonie IP et VoIP GnomeMeeting."
#: ../C/gnomemeeting.xml:77(primary) msgid "gnomemeeting" 
msgstr "gnomemeeting"

#: ../C/gnomemeeting.xml:110(title) ../C/gnomemeeting.xml:341
(title) ../C/gnomemeeting.xml:450(title) ../C/gnomemeeting.xml:489(title) msgid "Tip" 
msgstr "Note"
------------
After the hashmark, first there is the filename, and then in brackets the outermost xml tag. These pairs can appear multiple times if a string is appearing multiple times in the documentation. In most cases, you can just ignore this line :-) (it is used by the merging tools to put the translation to the right positions)
After this, there is first the msgid, which is plainly the original english string, and after this the translated string. 


Now, I suppose I'll have to change this way of work and it would
probably be better and more
"professional". That's great.
You can still use vi, sometimes I use it for the GUI translation, too. If there are a lot of changes, or ones is starting from scratch, it is more convenient to use a tools designed for po translation, the ones I know of are kbabel (part of KDE, my preferred one) and gtranslator (never used it ...). Kbabel (same may be true for gtranslator) features spell checking, easy navigation of the po file ("go to next untranslated message"), use of a compendium (you can use for example the gnomemeeting gui translation and search for a message, even simply copy identical messages automatically). 


I had a look today on
http://kvota.net/doc-l10n/by-modules.html#gnomemeeting to get some examples
and try to understand how it works but I must say I don't see.
Could you please explain a bit the way for me to maintain
gnomemeeting.xml in the future ?
What is a po ? What is the POT file ? What are the principles now ?
A po is the file holding the translation. po_t_ is a template, it just holds the original strings. Whenever the documentation is updated, a new pot is created automatically, and a new po is created from the old translation. Any unchanged strings are taken from the old po, slightly changed strings are marked as "fuzzy" (e.g. some corrected typos) and new strings will appear as untranslated. Just download the new po, incorporate any needed changes into it and commit (or let commit) it to cvs. The translated xml is automatically created from the po and the english gnomemeeting.xml. 


May be you could email me directly to avoid polluting the devel list ?
(ph_dot_l_at_libertysurf_dot_fr)

An other point : is there any way to be aware that gnomemeeting is
available on
http://kvota.net/doc-l10n....... ?
I am waiting for Damien to commit the changes to cvs. Afterwards the change have to be announced to the right people to let them change some scripts. When this is done, gnomemeeting will appear on the above mentioned page, but I will it announce to gm-devel when the change is completed. 


In advance, thank you for your help,
greetings,

PhL


Greetings,

Stefan


--
Stefan Brüns / Kastanienweg 6 - Zimmer 1206 / 52074 Aachen mailto:lurch gmx li http://www.kawo1.rwth-aachen.de/~lurchi/ phone: +49 241 169-4206 mobile: +49 160 3797725 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : /archives/attachments/20050729/cbcff03f/attachment.bin ------------------------------ Message: 3 Date: Sat, 30 Jul 2005 13:34:17 +0200 From: Daniel Huhardeaux <devel tootai net> Subject: Re: [GnomeMeeting-devel-list] Re: Moving to gnome-doc-utils (Damien Sandras) To: GnomeMeeting development mailing list <gnomemeeting-devel-list gnome org> Message-ID: <42EB65B9 5090108 tootai net> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Stefan Bruens a �it : 


[...]
You can still use vi, sometimes I use it for the GUI translation, too. If there are a lot of changes, or ones is starting from scratch, it is more convenient to use a tools designed for po translation, the ones I know of are kbabel (part of KDE, my preferred one) and gtranslator (never used it ...). Kbabel (same may be true for gtranslator) features spell checking, easy navigation of the po file ("go to next untranslated message"), use of a compendium (you can use for example the gnomemeeting gui translation and search for a message, even simply copy identical messages automatically). 
You also have QT Linguist
-- Daniel
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]