lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: European languages support?


From: Jan Nieuwenhuizen
Subject: Re: European languages support?
Date: Sun, 07 Nov 2004 11:14:48 +0100
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)

Bertalan Fodor writes:

> I can see that 2.4.0 is not able to correctly handle characters that
> are not in the bad old latin1 encoding - if they are written with TeX
> markup, the spacing is bad.

The patch below fixes TeX encoding.  I do not expect a fix for
PostScript any time soon, probably not even in 2.4.

> May I ask for an explicit announce in the ChangeLog,

This is in 2.5.x now and marked (backportme) but it's not in 2.4 yet,
I expect we'll have another week or so before releasing 2.4.2.

Jan.

\paper{
   inputencoding = #"TeX"
}
<<
   \new Voice {
       c' d' e' f'
   }
   \addlyrics {
        \'Ar -- v\'iz -- "t\H{u}" -- "r\H{o}"
   }
>>


Index: ChangeLog
===================================================================
RCS file: /cvsroot/lilypond/lilypond/ChangeLog,v
retrieving revision 1.2780.2.2
diff -p -u -r1.2780.2.2 ChangeLog
--- ChangeLog   31 Oct 2004 00:07:35 -0000      1.2780.2.2
+++ ChangeLog   7 Nov 2004 10:15:39 -0000
@@ -1,3 +1,10 @@
+2004-11-07  Jan Nieuwenhuizen  <address@hidden>
+
+       * tex/lilyponddefs.tex: If no inputencoding use latin1.
+
+       * scm/framework-tex.scm (font-load-command): Use T1 if no
+       font-encoding set.
+ 
 2004-10-31  Han-Wen Nienhuys  <address@hidden>
 
        * Documentation/user/preface.itely (Notes for version 2.4):
Index: scm/framework-tex.scm
===================================================================
RCS file: /cvsroot/lilypond/lilypond/scm/framework-tex.scm,v
retrieving revision 1.44
diff -p -u -r1.44 framework-tex.scm
--- scm/framework-tex.scm       29 Oct 2004 20:30:26 -0000      1.44
+++ scm/framework-tex.scm       7 Nov 2004 10:15:39 -0000
@@ -60,7 +60,8 @@
      "\n"
      "\\def\\" (tex-font-command font) "{%\n"
      ;; UGH.  Should be handled via alist.
-     (if (equal? "Extended-TeX-Font-Encoding---Latin" font-encoding)
+     (if (or (equal? "Extended-TeX-Font-Encoding---Latin" font-encoding)
+            (not font-encoding))
         "  \\lilypondfontencoding{T1}"
         "  ")
      "\\lilypond" (tex-font-command font)
Index: tex/lilyponddefs.tex
===================================================================
RCS file: /cvsroot/lilypond/lilypond/tex/lilyponddefs.tex,v
retrieving revision 1.113
diff -p -u -r1.113 lilyponddefs.tex
--- tex/lilyponddefs.tex        23 Oct 2004 19:45:40 -0000      1.113
+++ tex/lilyponddefs.tex        7 Nov 2004 10:15:39 -0000
@@ -195,7 +195,12 @@
        %% As a safety guard, don't produce auxiliary files.
        \nofiles
 
-       \usepackage[\lilypondpaperinputencoding]{inputenc}
+       %% FIXME: workaround non-existent TeX.def.
+       \def\TeXdef{TeX}\ifx\TeXdef\lilypondpaperinputencoding
+         \usepackage[latin1]{inputenc}
+       \else
+         \usepackage[\lilypondpaperinputencoding]{inputenc}
+       \fi
        \pagestyle{empty}
 
        \lilypondifundefined{lilypondclassic}

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org




reply via email to

[Prev in Thread] Current Thread [Next in Thread]