Hello,

for most screenshots the language indeed doesn't matter very much. But there are some that consist _only_ of text (of menus, for example) or where the text plays an important role. So I'm in favour of allowing localized images, no translator is forced to provide them if he or she feels that the text needs more maintenance at the moment.

Daniel

? ???, 05/11/2008 ? 14:59 +0100, Roman Joost ?????:

Hi folks,

we're close to migrate the manual content. There is one thing which I want to discuss on the mailing list: the need of localized images (providing German, French, etc screenshots for the readers).

The regular version of xml2po doesn't support localized images or screenshots. The current way of adding a german, french or korean screenshot to the manual is by separating them using the lang tag. This is normally not supported anymore by the regular version of xml2po.

Localized screenshots are mandatory for a good documntation. I don't quite understand your statement about xml2po not supporting them, it's perfectly supported. All GNOME documentation go with localized screenshots.

On Wed, Nov 5, 2008 at 11:09 PM, Nickolay V. Shmyrev wrote:

Localized screenshots are mandatory for a good documntation.

+1

Localized screenshots are a must. Users are not supposed to know English so good that they can tell one term from another on a screenshot when referenced from text.

Alexandre

Nickolay V. Shmyrev (Mittwoch, 5. November 2008, 21:09):

Localized screenshots are mandatory for a good documntation. I don't quite understand your statement about xml2po not supporting them, it's perfectly supported. All GNOME documentation go with localized screenshots.

How do you make it with xml2po?

Ulf

? ???, 05/11/2008 ? 23:52 +0100, Ulf-D. Ehlert ?????:

Nickolay V. Shmyrev (Mittwoch, 5. November 2008, 21:09):

Localized screenshots are mandatory for a good documntation. I don't quite understand your statement about xml2po not supporting them, it's perfectly supported. All GNOME documentation go with localized screenshots.

How do you make it with xml2po?

Ulf

xml2po puts md5 sum for each image mentioned in xml document so translator just knows that something is changed.

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all. #: C/evince.xml:155(None)
msgid ""
"@@image: 'figures/evince_start_window.png'; " "md5=7f4da5e33bcac35738a268d93d497d47" msgstr ""
"@@image: 'figures/evince_start_window.png'; " "md5=7f4da5e33bcac35738a268d93d497d47"

Separate folder with translated images is created and the same structure of images is put there. The translated document is put there as well. So you need to build the structure:

C/figures/a.jpg C/doc.xml
de/figures/a.jpg
de/de.po

and after xml2po it will be

de/figures/a.jpg de/doc.xml
de/de.po

all translated

On Wed, 5 Nov 2008 14:59:06 +0100, Roman Joost wrote:

we're close to migrate the manual content. There is one thing which I want to discuss on the mailing list: the need of localized images (providing German, French, etc screenshots for the readers).

What is the trget for this ? The actual images at http://docs.gimp.org/ appears to be already translated (I checked French and German).

Cristi

On Thu, Nov 6, 2008 at 4:43 AM, Alexandre Prokoudine wrote:

On Wed, Nov 5, 2008 at 11:09 PM, Nickolay V. Shmyrev wrote:

Localized screenshots are mandatory for a good documntation.

+1

+1 more
We need a screenshot with our mother tongue. please donot assume everyone can read english or knows alphabats

Nickolay V. Shmyrev (Donnerstag, 6. November 2008, 00:19):

xml2po puts md5 sum for each image mentioned in xml document so translator just knows that something is changed.

That's a nice feature, but it doesn't work for us: xml2po uses the path of the image ("
which are valid references only when browsing the HTML file.

Of course, we could apply yet another patch to xml2po...

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all. #: C/evince.xml:155(None)
msgid ""
"@@image: 'figures/evince_start_window.png'; " "md5=7f4da5e33bcac35738a268d93d497d47" msgstr ""
"@@image: 'figures/evince_start_window.png'; " "md5=7f4da5e33bcac35738a268d93d497d47"

We will always get md5="THIS FILE DOESN'T EXIST".

In any case this has nothing to do with localized images.

Separate folder with translated images is created and the same structure of images is put there. The translated document is put there as well. So you need to build the structure:

C/figures/a.jpg C/doc.xml
de/figures/a.jpg
de/de.po

and after xml2po it will be

de/figures/a.jpg de/doc.xml
de/de.po

all translated

This has nothing to do with xml2po supporting localized images. The image references will just be the same in "C/doc.xm" and "de/doc.xml".

So if we want to keep on providing localized images - and IMO we should -, we can

(a) use a patched version of "xml2po" in order to output messages like msgid ",
(b) change the directory structure so that images references alway point to the right image; this will have to work with HTML, PDF, and ODF, though.

Solution (a) is easy - and ugly. But we have never thought about (b)...

Ulf

I think it would be nice that every language has its own screenshots. In many of the images can be edited only the text, using the clone and text tool, and it's not neccessary to take them again, just change the language.

Linux User #384686 #include< David Padrón Álvarez > int main(){ /* Universidad de las Ciencias Informáticas Facultad de Bioinformática e Información Biomédica */ using namespace Estudiante ; RealTimeEncoder encoder; NetProtocols protocol=encoder.detect(); }return 0;