Re: Non-latin1 characters (was: Lyricsto skips notes with melisma's in 2.2)
On Thu, 13 Jan 2005 12:35:07 +0100, Mats Bengtsson <[EMAIL PROTECTED]> wrote: > MichaÅ DwuÅnik wrote: > > On Wed, 12 Jan 2005 14:42:37 +0100, Mats Bengtsson > > <[EMAIL PROTECTED]> wrote: > > > >>I don't remember from the top of my head what version of LilyPond > >>you use. In version 2.2, it was possible to set the input and > >>font encoding using > >>\header{ > >> fontencoding="..." > >> inputencoding="..." > >>} > >> > > > > That _was_ nice :), and let me do some tricks with latex intermediate > > file, after willingly crashing lilypond by not defining the encoding and > > using non-latin1 characters inside the piece :) > > Did you see > http://lists.gnu.org/archive/html/lilypond-user/2003-08/msg00061.html > which shows how to specify the font that LilyPond uses for lyrics > (or other textual annotations) using the font-name property? > Again, this is something that works up to version 2.2 but probably > not longer. > Yes. Instead of the hacks done by you for version from this thread I "invented" something else, which included adding proper inputencoding and fontencoding to the header of intermediate file, together with font-substitution packages like qtimes (that let me avoid looking into the font directory, which is not my favourite, and in the same time utilize my, maybe small but existing, LaTeX experience. The output was very nice, but the way of dealing with the files was not so, that's why I tried to move to version 2.4 and do +/- the same. I find 2.4 much more comfortable with the small annoyance described before. Both 2.2 way and 2.4 way is not something I would recommend to a fellow composer, but I hope to be able to do so when 2.6 appears. I admit, that I shouldn't pay to much attention to that and wait for 2.6, but in the same time I would really like to avoid having to wait for 2.8, because some working mechanism was discarded. (Please do not treat it as doubting in lilypond developers, it's just a bitter experience from some other GNU projects hunting for the ultimate solution, which is always "to come in the next version"). Thanks for your help MichaÅ PS:I feel like I'm saying the same thing for the n-th time, apologies for the bored PS2: We _want_ national characters, and if someone needs an example - the difference between "doing a favor" and, err.. "having oral intercourse" is only l or \l in TeX code PS3: http://www.lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Integrating-LaTeX-and-music.html shows that even for 2.5 different encodings are usable, but very far from the quality of the engraving itself, and that would be a pity to have perfect notes with badly aligned text with shifts. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Non-latin1 characters (was: Lyricsto skips notes with melisma's in 2.2)
MichaÅ DwuÅnik wrote: On Wed, 12 Jan 2005 14:42:37 +0100, Mats Bengtsson <[EMAIL PROTECTED]> wrote: I don't remember from the top of my head what version of LilyPond you use. In version 2.2, it was possible to set the input and font encoding using \header{ fontencoding="..." inputencoding="..." } That _was_ nice :), and let me do some tricks with latex intermediate file, after willingly crashing lilypond by not defining the encoding and using non-latin1 characters inside the piece :) Did you see http://lists.gnu.org/archive/html/lilypond-user/2003-08/msg00061.html which shows how to specify the font that LilyPond uses for lyrics (or other textual annotations) using the font-name property? Again, this is something that works up to version 2.2 but probably not longer. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Non-latin1 characters (was: Lyricsto skips notes with melisma's in 2.2)
On Wed, 12 Jan 2005 14:42:37 +0100, Mats Bengtsson <[EMAIL PROTECTED]> wrote: > I don't remember from the top of my head what version of LilyPond > you use. In version 2.2, it was possible to set the input and > font encoding using > \header{ >fontencoding="..." >inputencoding="..." > } > That _was_ nice :), and let me do some tricks with latex intermediate file, after willingly crashing lilypond by not defining the encoding and using non-latin1 characters inside the piece :) > If you use version 2.4, don't spend too much energy on solving these > problems since a new solution is already (almost) implemented in > the latest development versions and it seems that the release of > the next stable version 2.6 is not in the very far future. > I found my solution (involving sed) after some struggle, and to avoid that struggle I proposed adding something to the docs, like an example of what strange glyphs different people use in their own languages. You may be sure that I will be one of the first people to try 2.6 utf features :). Of course if 2.6 is due in something like 1 month, we can leave it, but if it's 6 months I would consider adding some hints or expanding "embedded TeX" example. > > to have a more generous example on "TeX" encoding for the use of > > non-fully-latin alphabet > > users ? And a clear remark, that one should probably not try to write > > his/her > > national characters "normally" (like latin2 encoding), or preprocess > > the file to produce TeX > > equivalents before running lilypond. That's the part I feel is missing in 2.4 documentation - that if you really want something in e.g. latin2 - use TeX encoding. I really have spent lots of time getting my test files processed with no errors, and seeing completely messy output afterwards, regardless of defining > \header{ >fontencoding="..." >inputencoding="..." > } This applies to section 7.4.1 of the 2.4 documentation - trying both cp1250 and latin2 for the inputencoding (Linux and Windows install) , T1 for fontencoding, general \encoding "latin2" gave me only completely messy output, the only usable encoding being "TeX" and writing the Polish glyphs by \k{a}, \\'c and so on. In my private mail I keep a discussion with two other Polih guys, who hadn't ever managed to get fontencoding and inputencoding working for version 2.4 and in the same time reporting that it works within 2.2. For version 2.4 example of getting Polish glyphs follows: --- \encoding "TeX" \header{ title = "\k{a}\\'c\k{e}\l\\'n\\'o\\'s\.z\\'zi" composer = "\k{A}\\'C\k{E}\L\\'N\\'O\\'S\.Z\\'ZI" } \transpose c c' { << {c d e f g a b c' cis' c d e f g a b c' cis' } \addlyrics { "\k{a}" "\\'c" "\k{e}" "\l" "\\'n" "\\'o" "\\'s" "\.z" "\\'z" "\k{A}" "\\'C" "\k{E}" "\L" "\\'N" "\\'O" "\\'S" "\.Z" "\\'Z" } >> } - This lets us use all the needed glyphs (and many others), but is far from comfortable, version 2.2 example with : \header{ inputencoding = "cp1250" fontencoding = "T1" } was reported to work perfectly, and used the encoding "natural" for windows (latin2 for linux I suppose) . In version 2.4.2 --- \header{ nputencoding = "cp1250" fontencoding = "T1" } \transpose c c' { << {c} \addlyrics { Ä } >> } yields the following .log --- This is TeXk, Version 3.14159 (Web2C 7.4.5) (format=latex 2005.1.13) 13 JAN 2005 11:40 %&-line parsing enabled. **\nonstopmode \input test.tex (./test.tex (/usr/share/lilypond/2.4.2/tex/lilyponddefs.tex \lytempdim=\dimen102 \outputscale=\dimen103 (/usr/share/lilypond/2.4.2/tex/lily-ps-defs.tex)) (/usr/share/texmf/tex/latex/base/article.cls Document Class: article 2001/04/21 v1.4e Standard LaTeX document class (/usr/share/texmf/tex/latex/base/size10.clo File: size10.clo 2001/04/21 v1.4e Standard LaTeX file (size option) ) (...) (/usr/share/texmf/tex/latex/base/inputenc.sty Package: inputenc 2001/07/10 v0.99a Input encoding file (/usr/share/texmf/tex/latex/base/latin1.def File: latin1.def 2001/07/10 v0.99a Input encoding file )) so it clearly tries to use latin1 encoding, where it shouldn't. Shall we have an update like "Non latin1 (or maybe just latin2) inputencodings are deprecated in version 2.4, use TeX encoding and type the TeX equivalents of your national characters. If you do not feel comfortable with TeX equivalents please do some preprocessing replacing the needed characters by their TeX prefix represantation." in section 7.4.1 ? Best regards, and thanks for Graham and Mats for their infinite will of help. Michal ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user