On Tue, 26 Apr 2005 00:25:15 +0200 Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> Op di, 26-04-2005 te 01:05 +0300, schreef Heikki Johannes Junes: > > > The correct solution is to specify the encoding in each web page. > But, the > > question for the future is that should one solely stick to UTF-8 > encoding in the > > web pages? One engineering challenge here is that some of the pages > contain > > inclusions from the source files which may not be in UTF-8 format. > > > > All pages (except documentation of 2.4 and earlier) should be utf-8. > So, one (already) uses `makeinfo --enable-encoding` and specifies in .tely -files: @documentencoding utf-8 Seeking with `grep -R documentencoding *`, one finds Documentation/user/lilypond.tely:@documentencoding ISO-8859-1 this also should be Documentation/user/lilypond.tely:@documentencoding utf-8 and the encoding of the file be utf-8? Also, many of the .po -files are encoded with ISO-8859-1. Should they also be coded with utf-8? And finally, will pdf, ps, latex, html, and info -files be flawlessly produced in utf-8 format if everything is in utf-8? They should, but will they? -- Terveisin Heikki Junes _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
