On 04/04/2011 10:47 AM, Julien Rioux wrote:
On 04/04/2011 10:39 AM, Richard Heck wrote:
On 04/04/2011 10:26 AM, Julien Rioux wrote:
On 04/04/2011 8:19 AM, Pavel Sanda wrote:
Julien Rioux wrote:
oups, you're right :) I tried this and Part is not translated to
Partie in
output. I first though that there is still some translation work
left to be
done, since for example with german I correctly get Teil. But
actually
using Czech as document language (which is indicated as fully
translated
here: http://www.lyx.org/I18n-trunk ) I also get the untranslated
Part in
output. This seems like a bug. Thanks for pointing it out.
by output you mean .pdf or UI appearance? (UI might be not working
unless
your locales are not correctly installed for czech, ie until you are
able
to run the whole UI in cz.)
pavel
I mean in the pdf. It seems I have an old (texlive 2009) version of
refstyle.sty which does not support French. Still, we do have all the
machinery to translate these strings by ourselves, I am not sure that
we want to rely on refstyle.sty
For an example file see my comment to
http://www.lyx.org/trac/ticket/2295
I think our general policy with such things has been to send bug fixes
or enhancements to the package authors rather than to try to handle
things locally. It makes more sense in the long run.
Richard
But but but... why all the strings in the new file layouttranslations?
Why bother if we are to rely on latex packages to provide their own
translations? We have more supported languages in layouttranslations
than what is available in refstyle. Even for supported languages (say,
French in later versions of refstyle), can we be sure that our
translations and those of refstyle will be consistent? (e.g., Table vs
Tableau)
We are freezing the strings for the 2.0 cycle (for a good reason it
seems). Refstyle will keep moving, unless we ship our own version with
LyX. Is that the plan?
I think these are different issues. As far as I understand, the
layoutranslations file is used for two sorts of purposes: (i) Providing
translations for some layout information inside LyX; (ii) providing the
data used to translate theorem-related stuff in the LaTeX output. We do
(ii) because there is no translation support for this sort of thing in
LaTeX. The point of moving to refstyle was that it does provide
translation support, not that we would provide all the translations.
Still, I understand the desire to do this kind of thing, and there is a
correct way we can do it. And also contribute to refstyle at the same time.
The refstyle package allows the use of a custom configuration file
instead of refstyle.cfg. What we could do is produce our own
configuration file and allow users the choice to use it. This would
presumably be a per-document setting. I'm not sure if we can get this
working perfectly by 2.0, but we could still get the setting into the
file format, even without UI, right away, so we could at least get it
working by 2.0.1, say.
It should be fairly easy to write a python script to take the info in
layouttranslations and then produce a customized version of
refstyle.cfg, based on the latest version thereof. Once we had that, of
course, we could diff it and send a patch to Danie Els, who has been
very responsive in the past to our requests and would presumably be
happy to have lots of translations. So that's what I'd suggest we do.
Richard
