Till Rettig a écrit :
Hi John,
somehow the section names don't get translated in the pdfs that are
produced by "make doc". I can see they are translated on the compiled
version on the web, but why don't I get them? :(
I can't answer without more details: Git committish, some of the titles
that are not translated, your texi2html version.
I can't even build the docs with a ton of Ghostscript failures, so it
seems you succeed further than me.
Another question is: can I update snippets only for one language?
Now I made makelsr.py usage more common, there should be no longer
translated texidoc awaiting for being added to input/lsr, so if you make
changes to texidoc only in one language, running makelsr.py should not
apply other changes to input/lsr.
and how to do a po-update (is this also possible for only one
language, as well on the web branch)?
This should be documented in the CG, lilypond.org README and
TRANSLATION. If itsn't, I'll fix it.
It's possible to do it in one language if you commit only the file in
your language, but the number of lanugages doesn't matter; what matters
is updating PO on a one-minute fresh copy of the sources and pushing it
to git.sv.gnu.org 5 seconds after having updated PO, to avoid conflicts.
While doing the compilation I get some error messages about undefined
glyphs. I just installed all the fonts Graham recently mentioned, but
it points to my texlive installation which is not handled by the
package manager. Is this a common error that I just can ignore?
The messages are like:
pdfTeX warning: pdfetex (file
/usr/local/texlive/2008/texmf-dist/fonts/type1/ur
w/ncntrsbk/uncr8a.pfb): glyph `afii10097' undefined
IIRC I get this too; did you see a bug related to this in output?
John
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
