Re: lp with korean/utf8 lambda dvipdfmx
Closing this thread:
Already several weeks ago, I corrected the lyrics' syntax like this:
\addlyrics {
\override Lyrics . LyricText #'font-name = HYPillGi-Light
아 -- 리 -- 랑, _ 아 -- 리 -- 랑, _ 아 -- 라 -- _ 리 -- _ 요 __
아 -- 리 -- 랑 _ 고 -- _ 개 -- _ 로 _ 넘 -- 어 -- 간 -- 다.
나 -- 를 버 -- 리 -- 고 가 -- 시 -- 는 님 -- _ 은 __
십 -- 리 -- 도 _ 못 _ 가 -- _ 서 _ 발 -- 병 -- 난 -- 다.
}
Then because lilypond handles these fonts I chose an appropriate ttf and
compiled it. Though lilypond doesn't cooperate with lambda, the generated
snippet could then be embeddeded as an eps into the main document.
I intend to do the following things now:
* sending a bug report concerning lambda to lilypond.org
* getting to know more about that xelatex-stuff; this and other font-related
things won't be discussed here then.
Thanks to all so far
Minsu
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lp with korean/utf8 lambda dvipdfmx
Edit1:
Then because lilypond handles these fonts I chose an appropriate ttf and
compiled it.
== while it means a seperate .tex-document including \usepackage{cjk} which
could be compiled with latex as usual; lilypond was then easily capable to
work out the correct snippet.
Edit2:
Though lilypond doesn't cooperate with lambda, the generated
snippet could then be embeddeded as an eps into the main document.
== while this main .tex-document still uses hlatex (or say
\usepackage{hangul}) which can only be compiled with lambda on [EMAIL
PROTECTED]
민수 드림 *^^*
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lp with korean/utf8 lambda dvipdfmx
\addlyrics {
\override Lyrics . LyricText #'font-name = Woorin R
[...]
Where did you find this?
In a comment of `sakura-sakura.ly' which is part of the lilypond
bundle. I've already mentioned in my last email that this particular
bit of information is probably missing from the documentation.
However, as soon as you are familiar with `grobs' (graphical objects)
in lilypond you would have been able to find this by yourself.
1) Supposing one's system is utf8-based -- am I right that with
cjk.sty at default one has no access to other fonts (and characters
of them in a different encoding) than myoungjo (like pilgi)?
This is not correct. I said that in the TeXLive distribution only a
single Korean font, myoungjo, is present (due to storage limits), and
I also mentioned that Danai is providing a large set of Korean fonts
for the CJK package (in both KS and Unicode encoding).
-- But would it (only) be possible with \begin{CJK}[HL]{KS} if the
system is euckr-based?
The `HL' parameter selects the layout of the subfonts. The default is
`foo01', `foo02', etc., and the HLaTeX fonts differ from that, so you
must specify it explicitly. The `KS' indicates KS 5601 encoding (this
is EUC-KR basically).
Unicode encoded fonts always have the same subfont layout im my CJK
package, namely `fooXX' where `XX' are two lowercase hexadecimal
digits.
Otherwise with what switch exactly could one access them -- if the
necessary fonts are installed/converted?
If you have a Unicode encoded Korean font `foo', you have two
possibilities:
. \begin{CJK}{UTF8}{foo}
This starts a CJK environment with Unicode font `foo'.
. \begin{CJK}{UTF8}{}
...
\CJKfamily{foo}
This starts a CJK environment with Unicode encoding (using `song'
as the default font), and you then manually switch to font `foo'.
Again, we are going off-topic...
I've written some perl scripts to create proper Korean subfonts; in
the beginning of September, Danai has posted a large Makefile to the
CJK mailing list which uses them to do that automatically. Since this
is an extremely time consuming process (I think Danai reported 48
hours or so for all fonts) you should rather use his pre-built
packages!
2) Is it possible to work cjk.sty and hangul.sty (hlatex) in the
same document, if more than one fontenc would be loaded; what
fontencs would that be? And should the compilation be run with latex
or lamba then?
I have no idea, but honestly, I can't see an immediate reason to use
both at the same time.
3) phhh~ xelatex... another door to push open...
Would this be the missing link or, is this a even replacement for
hlatex/cjk?
Well, it makes life easier since both lilypond and xelatex use the
same mechanism (this is, fontconfig) to select and access fonts;
additionally, both programs understand UTF-8 only, and neither of them
needs subfonts but can use the TTFs directly.
And what's the difference to lambda~?
lambda is the LaTeX macro package on top of Omega, a TeX extension.
The latter is no longer developed since John Plaice and Yannis
Haralambous, the original authors, have no interest in that any more,
for various reasons. It is a painful story -- both John and Yannis
produced fantastic papers but delivered vaporware mostly. It was
always badly documented, full of bugs and never really maintained.
The TeX community has waited 10 years or so for progress; today one
can say it's dead. The future is XeTeX and LuaTeX which both use
ideas from Omega.
unh... before entering the next level i have in mind to learn more
basic things about (international) font specs! -- I'll get that
recent book fonts encodings :)
This isn't really necessary. Just stay with Unicode (or rather,
UTF-8).
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lp with korean/utf8 lambda dvipdfmx
Hello Werner!
I've never used HLaTeX directly -- everything is in Korean which I
don't understand
Of course I wouldn't expect that; But the hlguide.pdf (or hlguide-u.tex)
nevertheless contains many English expressions -- and you're familiar with
latex ;-)
Step by step I'll reach my goal.
This hint has done it:
You've done a syntax error:
\addlyrics {
\override #'(font-name . 휴먼우린체,Woorin R)
[...]
This must be
\addlyrics {
\override Lyrics . LyricText #'font-name = Woorin R
[...]
Where did you find this?
I tested the engraving successfully several times with different fonts, without
any extra effort; meanwhile I found one called HYPillGi-Light yet and, the
result looks quite nice :-))
---
The status quo is that I will embed this lilypond-eps into the main document,
which uses hlatex/lambda. Within hlatex, one can switch the (Korean) fonts
easily. -- And if possible, within hlatex I would like to desribe via a listing
(what means some lines of verbatim-code) how to change fontencs and -families
with cjk.sty/utf8. I'd like to show if it's really possible to typeset with
(e.g.) pilgi with cjk.sty or not -- therefor I needed the lyrics.
All the same I partly understand now what's about this 'font-selection-
business'. There are still some questions left, so sooner or later I'll take a
closer look at your cjk-mailing-list (probably located at comp.text.tex), I
guess.
But before, just to get ahead with my essay, please tell me a few things more
(though the questions may sound stupid~).
1) Supposing one's system is utf8-based -- am I right that with cjk.sty at
default one has no access to other fonts (and characters of them in a different
encoding) than myoungjo (like pilgi)? -- But would it (only) be possible with
\begin{CJK}[HL]{KS} if the system is euckr-based?
Otherwise with what switch exactly could one access them -- if the necessary
fonts are installed/converted?
2) Is it possible to work cjk.sty and hangul.sty (hlatex) in the same document,
if more than one fontenc would be loaded; what fontencs would that be? And
should the compilation be run with latex or lamba then?
3) phhh~ xelatex... another door to push open...
Would this be the missing link or, is this a even replacement for hlatex/cjk?
And what's the difference to lambda~?
unh... before entering the next level i have in mind to learn more basic things
about (international) font specs! -- I'll get that recent book fonts
encodings :)
Thanks a lot!
Minsu
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lp with korean/utf8 lambda dvipdfmx
@till Sorry, s.th. seemed to be wrong with the gmane-server -- the specific messages weren't displayed. So I could read your post just a few minutes ago. Your post is quite interesting. I'll look at that xetex-stuff later, probably after the weekend. ifxetex.sty is (of course) installed anyhow. thanx! ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lp with korean/utf8 lambda dvipdfmx
What exactly do you mean? HLaTeX, as far as I know, provides a
complete `HFSS' (Hangul Font Selection System) for Korean which
should not interact with non-Korean typesetting.
I installed hlatex next to CJK.sty etc to get the power of both; it
seems now logical not being able to use T1 next to HFSS!-?
I've never used HLaTeX directly -- everything is in Korean which I
don't understand :-)
...though in his documentation of hlatex Mr Un used a glyph that
looks like \ding{43}~ You may google for hlguide.pdf, it's on p22
then.
Within my CJK package, a command \ding is used only if you load
pinyin.sty.
And it may be from interest, though the default font is MyoungJo the
Hangul lyrics came out in 고딕 ('gotik', what's equivalent to 'sans
serif'); so I guess sans serif is the default family for lyrics in
lilypond (and latex).
The default is what fontconfig provides as the default. This can be
configured for your platform.
How to change the font is explained in GNU LilyPond.html | 8.1.7
Font Selection (resp. lilypond.pdf) but, I still can't cope with
it
You've done a syntax error:
\addlyrics {
\override #'(font-name . 휴먼우린체,Woorin R)
[...]
This must be
\addlyrics {
\override Lyrics . LyricText #'font-name = Woorin R
[...]
[Is there an example to change the lyric font somewhere in the new
docs? I can only find the `sakura-sakura.ly' example file...]
My knowledge of Pango font trees is nonexistent, so I can't comment
your further observations.
B) lilyponds detects them, but cannot display them; actually, these
fonts seem to be .ttf only
Well, at least the font `dotum.ttf' (Baekmuk Dotum version 1.2) is
bad: It contains a `name' table where all names are `.null' (BTW, this
font makes gs 8.55 hang or working so slowly that I wasn't patient
enough to wait until it has finished -- the new 8.61, however, is just
fine). lilypond needs such a valid `name' table to construct a
Type 42 font which can be then embedded into the PS file.
Hmm, it seems that all Baekmuk fonts are affected: Both `gulim.ttf'
and `batang.ttf' also don't contain valid glyph names. With other
words: Those three fonts can't be used with lilypond.
I don't have this `Woorin' font you are actually using but maybe this
causes problems too.
I wonder why lilypond doesn't find any fonts beneath
/usr/local/texlive/2007/*
You have to configure the `fontconfig' library to look there for fonts
too. Maybe it's simpler to create symlinks...
-- even though it is embedded in latex?
LaTeX uses a complete different mechanism to locate fonts (the
`kpathsea' library).
And especially it converted the default myoungjo into a 'sans serif'
-- without make-pango-font- tree? What am I supposed to enter for
the make-pango-font-tree for the correct latex/CJK-fonts?
Here it is getting complicated. In TeXLive, I've used the old HLaTeX
fonts which are a bunch pf subfonts with 256 glyphs each. This is
something fontconfig doesn't handle.
D) I did read all the stuff before. And it wouldn't help me much
from becoming more confused~ E.g. lilypond is scanning the
.tex-document and detects the Hangul auto- matically and converts it
correctly. So why would it not be possible to specify a font
/before/ the {lilypond}-block? ...
You have to use a Korean font which can be both accepted by LaTeX and
lilypond. The simplest route is to use a TTF:
. Put it into a directory where lilypond can find it (the default
location in your GNU/Linux box should be just fine).
. Put a symlink of this font into a directory where LaTeX can find
it (an appropriate place within your TEXMF tree).
. Call ttf2tfm (with proper options) to create a bunch of subfont
TFMs in Unicode encoding.
. Create a proper FD file for the CJK package (similar to
`c70mj.fd').
. Register the TTF properly for dvipdfmx (and pdftex).
The use of CJK TrueType fonts with pdftex and dvipdfmx is extensively
documented in the file `doc/pdfhowto/HOWTO.txt' in the CJK package.
Another possibility is to use TTFs for lilypond and the same fonts
converted to PS Type 1 subfonts for LaTeX. Danai SAE-HAN (韓達耐)
[EMAIL PROTECTED] has provided the latter for the HLaTeX fonts
-- I think he has created Debian packages, but I don't know where you
can find it in the internet.
Look around in the forums provided by KTUG (the Korean TeX Users'
Group); you might also look up the archives of the CJK mailing list.
At first: declaring s.th. else than
\begin{CJK}{UTF8}{mj}
simply does not work!
This is correct. On TeXLive, there is only the `mj' font in Unicode
encoding.
And following the steps .../latex/CJK/doc/CJK.txt|Korean input I
haven't been able neither to write a document with e.g.
\begin{CJK}{KS}{mj}...\end{CJK} with/without [HL] nor to get any
\CJKchar except with [UTF8]. -- How can I change from {UTF8}{mj} to
([HL]){KS}{pg}?
Well, `KS' is KS 5601 encoding, not Unicode! You can use `iconv' to
convert between
Re: lp with korean/utf8 lambda dvipdfmx
A follow-up: In TeXLive, I've used the old HLaTeX fonts which are a bunch pf subfonts with 256 glyphs each. This is something fontconfig doesn't handle. Everything can be greatly simplified by using XeLaTeX since this program uses fontconfig too. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lp with korean/utf8 lambda dvipdfmx
Hi, I just had my first trials with XeteX today: it works!
The trick is only to use the ifxetex package. It provides the \ifxetex \else
\fi environment. You just have to put everything sepcific to xetex into the
first part, that is, mainly everything about font specification. You will
have to use this also in the main text if you want to make xetex specific
font switiching there. I guess the \else part can even be empty as it just
enables the lilypond run with latex. Or then you could define the utf8
option here. I just included some non latin scripts in my document and it
compiled without complaint about any encoding problems and so on.l i just
can say: GREAT.
I post the file I was using:
%%begin file
\documentclass[DIV=12]{scrreprt}
\usepackage{ifxetex}
\ifxetex
\usepackage{fontspec}
\setmainfont{FreeSans}
%\usepackage[xetex]{graphicx}
\usepackage{graphicx}
\else
\usepackage[utf8]{inputenc}
\usepackage{graphicx}
\usepackage{pdfpages}
\fi
\usepackage[russian,english]{babel}
\listfiles
\begin{document}
A funny example.
\begin[quote]{lilypond}
{a4 b a c }
\end{lilypond}
And some other language with babel: \selectlanguage{russian}
Что-то здесь не то, но я точно еще не знаю, на что надо посмотреть.
\selectlanguage{english}
And without:
Что-то здесь не то, но я точно еще не знаю, на что надо посмотреть.
ぎ
\end{document}
%end file
Greetigns
Till
kaputnik wrote:
Indeed, the use of `latex' is hard-coded currently. While lambda is a
rather dead end, users might become interested in using XeTeX. This
is worth a bug report IMHO.
I've been thinking about that, too.
--
View this message in context:
http://www.nabble.com/lp-with-korean-utf8-lambda-dvipdfmx-tf4817888.html#a13927625
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lp with korean/utf8 lambda dvipdfmx
Again thanks for your reply, Werner.
Hopefully you are still in the mood for discussing this topic.
I therefore successfully integrated all that hlatex-stuff into my
texlive. At first it seemed to work fine -- until some small
disadvantages came up (e.g. emphasized Latin appear slanted and not
italic, ther's no use of T1- fonts like marvosym, pifont,
latexsym,...
What exactly do you mean? HLaTeX, as far as I know, provides a
complete `HFSS' (Hangul Font Selection System) for Korean which should
not interact with non-Korean typesetting.
Ehm, because i've been texing for about half a year now I only /start/ to
understand what's all about that fonts and encodings stuff~
I installed hlatex next to CJK.sty etc to get the power of both; it seems
now logical not being able to use T1 next to HFSS!-? ...though in his
documentation of hlatex Mr Un used a glyph that looks like \ding{43}~
You may google for hlguide.pdf, it's on p22 then.
The latest stage with my Korean folksong is that I just happily finished
cleaning it -- what just means all the notes and lyrics are wellformed
and positioned and formatted correctly now :-)
The lilypond code is nested as a paragraph in a .tex with CJK.sty-document.
And it may be from interest, though the default font is MyoungJo the Hangul
lyrics came out in 고딕 ('gotik', what's equivalent to 'sans serif'); so I
guess
sans serif is the default family for lyrics in lilypond (and latex).
How to change the font is explained in
GNU LilyPond.html | 8.1.7 Font Selection (resp. lilypond.pdf) but, I
still can't cope with it~ Anyhow, usable fonts can be found with
$ lilypond -dshow-available-fonts blabla | more ...and there are hundreds.
First, it tried just to add this \override-line:
[Listing1]
code
\documentclass[12pt,a4paper]{article}
\usepackage[utf8]{inputenc}
\usepackage{CJKutf8}
\usepackage[T1]{fontenc}
\begin{document}
\begin{CJK}{UTF8}{mj}
Arirang-lyrics:
\par
아 -- 리 -- 랑, 아 -- 리 -- 랑, 아 -- 라 -- 리 -- 요,\\
아 -- 리 -- 랑 고 -- 개 -- 로 넘 -- 어 -- 간 -- 다.\\
나 -- 를 버 -- 리 -- 고 가 -- 시 -- 는 님 -- 은\\
십 -- 리 -- 도 못 -- 가 -- 서 발 -- 병 -- 난 -- 다.\par
Arirang-melody:
\par
\begin[line-width=100,staffsize=16,fontload]{lilypond}
\relative c' {
\key d \minor
\time 3/4
c4. d8 c8[ d] f4. g8 f8[ g] a4 g8[ a] f8[ d] c4.( d8 c4) \break
f4. g8 f8[ g] a8[ g] f8[ d] c8[ d] f4. g8 f4 f2. \break
c'2 c4 c4 a4 g4 a4 g8 a\noBeam f8[ d] c4.( d8 c4) \break
f4. g8 f8[ g] a8[ g] f8[ d] c8[ d] f4. g8 f4 f2.
}
\addlyrics {
\override #'(font-name . 휴먼우린체,Woorin R)
아- 리- 랑, _ 아- 리- 랑, _ 아- 라- _ 리- _ 요 __
아- 리- 랑 _ 고- _ 개- _ 로 _ 넘- 어- 간- 다.
나- 를 버- 리- 고 가- 시- 는 님- _ 은 __
십- 리- 도 _ 못 _ 가- _ 서 _ 발- 병- 난- 다.
}
\end{lilypond}
\end{CJK}
\end{document}
/code
lilypond cuts off like the following:
...
lilypond wird ausgeführt...GNU LilyPond 2.10.33
»snippet-map.ly« wird verarbeitet
Analysieren...
»arirang-cjk-test.tex« wird verarbeitet
Analysieren...
arirang-cjk-test.tex:83:26: Fehler: syntax error, unexpected SCM_TOKEN,
expecting LYRICS_STRING or STRING or STRING_IDENTIFIER
\override
#'(font-name . Woorin R)
arirang-cjk-test.tex:74:16: Fehler: Fehler gefunden, musikalischer
Ausdruck wird ignoriert
...
The result is only the staffs are engraved without the lyrics.
The next I tried was this:
[Listing2]
code
\documentclass[12pt,a4paper]{article}
\usepackage[utf8]{inputenc}
\usepackage{CJKutf8}
\usepackage[T1]{fontenc}
\begin{document}
\begin{CJK}{UTF8}{mj}
Arirang-lyrics:
\par
아 -- 리 -- 랑, 아 -- 리 -- 랑, 아 -- 라 -- 리 -- 요,\\
아 -- 리 -- 랑 고 -- 개 -- 로 넘 -- 어 -- 간 -- 다.\\
나 -- 를 버 -- 리 -- 고 가 -- 시 -- 는 님 -- 은\\
십 -- 리 -- 도 못 -- 가 -- 서 발 -- 병 -- 난 -- 다.\par
Arirang-melody:
\par
\begin[line-width=100,staffsize=16,fontload]{lilypond}
\paper {
myStaffSize = #16
#(define fonts
(make-pango-font-tree 휴먼명조
HYPillGi-Light
휴먼엑스포
(/ myStaffSize 16)))
}
\relative c' {
\key d \minor
\time 3/4
c4. d8 c8[ d] f4. g8 f8[ g] a4 g8[ a] f8[ d] c4.( d8 c4) \break
f4. g8 f8[ g] a8[ g] f8[ d] c8[ d] f4. g8 f4 f2. \break
c'2 c4 c4 a4 g4 a4 g8 a\noBeam
Re: lp with korean/utf8 lambda dvipdfmx
Hello Werner, nice to read from you :) Unfortunately, this is impossible because lilypond-book invokes latex only but, I need it to run lambda, so the mess showed up with the no files output-error only! Indeed, the use of `latex' is hard-coded currently. While lambda is a rather dead end, users might become interested in using XeTeX. This is worth a bug report IMHO. I've been thinking about that, too. You might try my CJK package for standard LaTeX instead... ... The CJK package comes with UTF-8 support. On TeXLive, some standard Korean fonts (taken from an older version of HLaTeX) have been provided both for KS encoding and UTF-8 (using virtual fonts for that). Yes, I used it in the beginning; but as you wrote in the latex/CJK/doc/CJK.txt|Korean input CJK does not emulate the behaviour of HLaTeX, it only supports its fonts. I therefore successfully integrated all that hlatex-stuff into my texlive. At first it seemed to work fine -- until some small disadvantages came up (e.g. emphasized Latin is shown slanted and not italic, ther's no use of T1-fonts like marvosym, pifont, latexsym,... and now the same with lilypond; hopefully someday a genius will solve all of it within latex3 ;) ). The functionality of CJK/CJKutf8 is quite impressive. But I switched to hlatex for a particular document now mainly because I couldn't access any hlatex-fonts and wasn't able to change the encoding either. (But this will probably be discussed at another forum ;) ) With hlatex I got all fonts now and additionally Korean formatting abilities. So I'll continue to write the document with hlatex. Nevertheless, I got another idea: After mispending hours on trying musixtex, I copied that lilypond-code into a new tex-file which uses CJK.sty -- et viol`a -- it works (for now). I really produced some snippets of staffs and notes :) Well, I still have to 'clean' them and, in the following I'll add the lyrics. When everything is OK, I'll convert the resulting .eps-files into jpeg, paste them into my hlatex-document and make that a pdf. A bit complicated but better than nothing. Unfortunately there's another small problem with CJK.sty (or say, more likely with my brain~). Until now, though I seemingly got all necessary fonts, I could still use only the default font myoungjo (mj) for Korean. But because I prefer pilgi (pg) for typesetting the lyrics here -- what can I do? Minsu -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lp with korean/utf8 lambda dvipdfmx
Hello Werner, nice to read from you :) Unfortunately, this is impossible because lilypond-book invokes latex only but, I need it to run lambda, so the mess showed up with the no files output-error only! Indeed, the use of `latex' is hard-coded currently. While lambda is a rather dead end, users might become interested in using XeTeX. This is worth a bug report IMHO. I've been thinking about that, too. You might try my CJK package for standard LaTeX instead... ... The CJK package comes with UTF-8 support. On TeXLive, some standard Korean fonts (taken from an older version of HLaTeX) have been provided both for KS encoding and UTF-8 (using virtual fonts for that). Yes, I used it in the beginning; but as you wrote in the latex/CJK/doc/CJK.txt| Korean input CJK does not emulate the behaviour of HLaTeX, it only supports its fonts. I therefore successfully integrated all that hlatex-stuff into my texlive. At first it seemed to work fine -- until some small disadvantages came up (e.g. emphasized Latin appear slanted and not italic, ther's no use of T1- fonts like marvosym, pifont, latexsym,... and now the same with lilypond; hopefully someday a genius will solve all of it within latex3 ;) ). The functionality of CJK/CJKutf8 is quite impressive. But I switched to hlatex for a particular document now mainly because I couldn't access any hlatex-fonts and wasn't able to change the encoding either. (But this will probably be discussed at another forum ;) ) With hlatex I got all fonts now and additionally Korean formatting abilities. So I'll continue to write the document with hlatex. Nevertheless, I got another idea: After mispending hours on trying musixtex, I copied that lilypond-code into a new tex-file which uses CJK.sty -- et viola -- it works (for now). I really produced some snippets of staffs and notes :) Well, I still have to 'clean' them and, in the following I'll add the lyrics. When everything is OK, I'll convert the resulting .eps-files into jpeg, paste them into my hlatex-document and make that a pdf. A bit complicated but better than nothing. Unfortunately there's another small problem with CJK.sty (or say more likely with my brain~). Until now, though I seemingly got all necessary fonts, I've still been able to use only the default font myoungjo (mj) for Korean. But because I prefer pilgi (pg) for typesetting the lyrics here -- what can I do? Minsu ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lp with korean/utf8 lambda dvipdfmx
I therefore successfully integrated all that hlatex-stuff into my texlive. At first it seemed to work fine -- until some small disadvantages came up (e.g. emphasized Latin appear slanted and not italic, ther's no use of T1- fonts like marvosym, pifont, latexsym,... What exactly do you mean? HLaTeX, as far as I know, provides a complete `HFSS' (Hangul Font Selection System) for Korean which should not interact with non-Korean typesetting. The functionality of CJK/CJKutf8 is quite impressive. But I switched to hlatex for a particular document now mainly because I couldn't access any hlatex-fonts and wasn't able to change the encoding either. The easiest thing for us (especially for me :-) is that you provide a real example attached to a mail (so that the encoding of the document doesn't get mangled). Old HLaTeX fonts are in EUC-KS encoding, while the newer ones use Unicode only, IIRC. So where's the problem with CJKutf8 and/or CJK? After mispending hours on trying musixtex, I copied that lilypond-code into a new tex-file which uses CJK.sty -- et viola -- it works (for now). I really produced some snippets of staffs and notes :) Hehe. Well, I still have to 'clean' them and, in the following I'll add the lyrics. When everything is OK, I'll convert the resulting .eps-files into jpeg, paste them into my hlatex-document and make that a pdf. A bit complicated but better than nothing. Hmm. You might contact the HLaTeX maintainers directly. Unfortunately there's another small problem with CJK.sty (or say more likely with my brain~). Until now, though I seemingly got all necessary fonts, I've still been able to use only the default font myoungjo (mj) for Korean. But because I prefer pilgi (pg) for typesetting the lyrics here -- what can I do? You mean the lyrics used in the music snippets? Assuming that you use 2.11.xx or 2.10.xx, this is no longer controlled by TeX but by LilyPond, so you have to look up LilyPond's documentation how to change the font. Otherwise, please send an example. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
lp with korean/utf8 lambda dvipdfmx
Hi forum!
I'm a German latex-user and new to lilypond.
My intention is to place a few lines of melody and lyrics of a wellknown Korean
folksong (Arirang) in a certain korean font into a latex-document, probably
within a minipage (or a table). All should end up in a PDF.
I entered \begin{lilypond} ... \end{lilypond} into the .tex-document then.
After finishing my first 'composition' following the main lp-doc and the
'regression/collated-files'-doc (near the end, for the multilingual section)
and, of course I'd like to see now how it looks like~
Unfortunately, this is impossible because lilypond-book invokes latex only
but, I need it to run lambda, so the mess showed up with the no files
output-error only!
((Nevertheless there's been some output: a .aux, .log and an .out-file,
seemingly without any use for now.))
Some more explanation:
My system is linux with utf8. Further, I use hlatex (Korean LaTeX), which I
have to include into the .tex-preamble with the obligatory \usepackage{hangul}.
On a non-UTF8-system, one can use simply pdflatex for creating PDFs directly.
In my case, a latex-document built with hlatex (based on EUC-KR/KS-encoding)
must be compiled into PDF in to steps:
$ lambda korean.tex
$ dvipdfmx korean.dvi
while lambda is some kind of latex-extension for 'switching' to UTF8 (otherwise
latex breaks off with too many errors).
So, now the only thing that had been formated is the lyrics in the particular
font~ For a temporary solution the musical notes could be handled by lilypond-
book and the lyrics by latex seperately. But before I wouldn't see any no
notes, I won't paste any lilypond-code here.
Are there any options then for lilypond to invoke lambda?
How would the example utf-8.ly in collated-files have been compiled, if
it's used with latex?
Thanks you
Minsu
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lp with korean/utf8 lambda dvipdfmx
Unfortunately, this is impossible because lilypond-book invokes latex only but, I need it to run lambda, so the mess showed up with the no files output-error only! Indeed, the use of `latex' is hard-coded currently. While lambda is a rather dead end, users might become interested in using XeTeX. This is worth a bug report IMHO. In my case, a latex-document built with hlatex (based on EUC-KR/KS-encoding) must be compiled into PDF in to steps: You might try my CJK package for standard LaTeX instead... Are there any options then for lilypond to invoke lambda? How would the example utf-8.ly in collated-files have been compiled, if it's used with latex? The CJK package comes with UTF-8 support. On TeXLive, some standard Korean fonts (taken from an older version of HLaTeX) have been provided both for KS encoding and UTF-8 (using virtual fonts for that). Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
