Adrien Rebollo wrote:
Hello,
I guess I am not the only translator fighting with the innumerable
variants in the layout strings.
Me, too (although I almost completed work)
All the layout strings are currently marked as translatable, and it is
up to the translator to decide if he should try to adapt them or not.
But, as I understand it from the manuals, some of the layouts are
language-specific. Obvious examples are the English or German letter
layouts.
Ideally, the German letter layouts should be removed completely. I guess
they were created at a time when localization of layout strings was not
supported. Maybe we can convince Jose to write a simple lyx2lyx script
that maps the German layouts onto the English ones.
It could be "en" for all the scientific publications and English
letters, "de" for the German letters, and "all" for the multi-usage
layouts. Only the strings from the files tagged "all" would go into
the po file.
Yes, that would be a good idea. However, I think it would be better to
have a "translatable" flag only. From the point of view of a Spanish
guy, it does not really matter whether the document is English or German
as long as it is non-translatable. The flag should also be used
internally by LyX. Otherwise, LyX will translate some label strings
accidentally.
Another nuissance is this:
msgid "Acknowledgement"
msgid "Acknowledgements."
msgid "Acknowledgements"
msgid "[Acknowledgements]"
msgid "Acknowledgement."
msgid "Acknowledgement \\arabic{acknowledgement}."
msgid "Acknowledgements:"
msgid "Acknowledgments"
msgid "Acknowledgement \\arabic{theorem}"
msgid "Acknowledgement @[EMAIL PROTECTED]"
msgid "Acknowledgement*"
Or this:
msgid "Definition"
msgid "Definition #:"
msgid "Definition."
msgid "Definition \\arabic{definition}."
msgid "Definition \\arabic{theorem}"
msgid "Definition #."
msgid "Definition*"
msgid "Definition @[EMAIL PROTECTED]"
There are many, many similar cases. Actually, I don't know what to do
about it.
Michael
