[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Regarding LSR translation work

From: Phil Holmes
Subject: Re: Regarding LSR translation work
Date: Fri, 4 May 2012 15:51:33 +0100

----- Original Message ----- From: "Federico Bruni" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: <address@hidden>
Sent: Tuesday, April 24, 2012 1:29 PM
Subject: Re: Regarding LSR translation work

2012/4/24 Phil Holmes <address@hidden>:
1) I don't understand what "say hello to LSR" means.

sorry, I meant "goodbye to LSR"

2) I don't really understand how LSR snippets are translated, so can't
comment knowledgably

See CG, 5.8.3, Updating translation committishes (last two paragraphs).

The translations are saved in "Documentation/MY-LANGUAGE/texidocs".
Running makelsr will copy the new translations to the relevant files.
That's why the committish stuff "breaks":

- a snippet gets a new committish
- only the latest language added has the latest makelsr committish and
therefore it's up-to-date for check-translation
- all the other languages will be out-of-date even if they are not

I'm afraid that the only way to avoid this is putting the english
texidoc="" and doctitle="" strings in Documentation/texidocs
and change accordingly.
Translators would then translate and track Documentation/texidoc/* and
ignore totally Documentation/snippets/

I hope that what I wrote makes sense.

Just having a little think about this.

I think the way to do this would be to have extract the texidoc and doctitle strings from the snippets and to put them into Documentation/texidoc/. In principle it would delete them from the snippet, and then put them back in again, as I believe it does for translated strings. However, that seems pointless - if it just copies the strings to the directory, the translators can monitor those, as they do for other documents.

Is that accurate?

Phil Holmes

reply via email to

[Prev in Thread] Current Thread [Next in Thread]