Le vendredi 21 mars 2008 à 18:39 -0300, Han-Wen Nienhuys a écrit : > 2008/3/20, Reinhold Kainhofer <[EMAIL PROTECTED]>: > > For the index page, I think it's a good idea to have automatic language > > selection, but from the on, all links should point to the files for the > > same > > language as the current page. > > That's not impossible, but you have to make sure you have proper > fallback if that page is not available in the language you want.
Would it be possible to be able to visit lilypond.org in a manually selected language (e.g. via "About automatic language selection" page or from each menu), falling back to English for untranslated pages, using subdomains (e.g. de.lilypond.org/web/about) or virtual subdirs (lilypond.org/fr/web/about) handled by mod_rewrite or other Apache plugins? This would prevent the user from opening a bunch of dialog boxes twice to change his preferred browsing language. > > BTW, is the automatic language selection (i.e. creating links without .html > > extension and adding the "Alternative languages" link on the bottom) > > implemented directly in makeinfo, or does lilypond's build system some more > > magic to get this? > > I think it's LP's magic. Yes, it is, see buildscripts/add_html_footer.py, especially process_links line 178. I'll have a look at dev/texi2html to help sorting out details like this when I find some time, maybe not before 4th April... I already wonder whether lastest texi2html version interprets -D "VAR VALUE" makeinfo option, which is needed for big page docs, and is also useful for automatic version number. It's doable to get the version number in a generated file $(outdir)/version.texi, but I don't know how to replace "-D bigpage" with texi2html. Cheers, John _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
