It is normal that 'dvips -Ppdf file.dvi' does not cope with the
following LaTeX file:
\documentclass[a4paper]{article}
\usepackage[latin1]{inputenc}
\usepackage[T1]{fontenc}
\begin{document}
Ã
\end{document}
unless you have installed some additional font files, but if
it cannot handle
\document
sÃn, 2004-04-18 kl. 23:14 skrev Erik Sandberg:
> On Sunday 18 April 2004 22.22, Jan Nieuwenhuizen wrote:
> > > But then, just for the
> > > experiment, I deleted that file and pasted your input into Emacs.
And
> > > the file compiled neatly. I lost the r in"g\aa r",though, and
that's
> > > part of
Ferenc Wagner wrote:
... can somebody explain the
origin of
warning: can't find ascii character: 243
and similar messages from LilyPond? I use straight latin1
encoding in my input files.
In addition to Jan's answer; if you want to get rid of the warning and
help LilyPond version <2.3 do a bette
Ferenc Wagner writes:
> This discussion is most interesting and very important.
No it isn't :-) That is, it would have been very important,
but 2.3.x has/is planned to have some true encoding support.
> warning: can't find ascii character: 243
LilyPond < 2.3.0 does not know about encoding. It
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Mats Bengtsson writes:
>
latexpackages = "[T1]fontenc, [swedish]babel"
>
>> I'm sure there are packages where not every package option can be
>> easily set by a separate command, but it's not necessary to
>> cope with those for the moment.
>
> O
Mats Bengtsson writes:
>>>latexpackages = "[T1]fontenc, [swedish]babel"
> I'm sure there are packages where not every package option can be
> easily set by a separate command, but it's not necessary to
> cope with those for the moment.
Ok. I've added to 2.2 CVS:
* scripts/lilypond.py:
Jan Nieuwenhuizen wrote:
The problem is the syntax of latexpackages. We need a syntax where we
can add individual options to each package. If you try to use the
package fontenc and add the option 'T1' using latexoptions, the option
will be included as an option to \documentclass and LaTeX will gi
Mats Bengtsson writes:
> Weird! Can you compile that following LaTeX file?
Sorry, ignore this, Twas a cut and paste problem.
> ---
> \documentclass[a4paper]{article}
>
> \usepackage[latin1]{inputenc}
>
> \begin{document}
> Han fører dødens så går
> \end{document}
Jan Nieuwenhuizen wrote:
Mats Bengtsson writes:
You don't need to change the font-name or add the t1enc package
unless you want to be able to search for the lyrics in Acrobat
or copy/paste them from Acrobat to some other file.
Could you elaborate? Is this about bitmap fonts, do we find those
Mats Bengtsson writes:
> You don't need to change the font-name or add the t1enc package
> unless you want to be able to search for the lyrics in Acrobat
> or copy/paste them from Acrobat to some other file.
Could you elaborate? Is this about bitmap fonts, do we find those
acceptable?
>
You don't need to change the font-name or add the t1enc package
unless you want to be able to search for the lyrics in Acrobat
or copy/paste them from Acrobat to some other file.
Also, with most text editors (i.e. with editors that can
output latin1 coded text), you can just write the letters
as us
Oddgeir Finstad <[EMAIL PROTECTED]> writes:
> An example .ly file with Scandinavian lyrics would probably be the
> easiest way out for me. Or maybe a table with instructions of how to
> type the actual letters? Or some relevant pointers?
The absolutely simplest way of entering Scandinavian lyrics
On Sunday 18 April 2004 22.22, Jan Nieuwenhuizen wrote:
> > But then, just for the
> > experiment, I deleted that file and pasted your input into Emacs. And
> > the file compiled neatly. I lost the r in"g\aa r",though, and that's
> > part of the original problem.
>
> Ah, maybe you should use quotes
Oddgeir Finstad writes:
> As for the input file: Yes, as far as I could see it was identical. I
> had copied it from your mail and pasted it into gedit, which is the
> editor I have been using.
Ugh. What a mess.
> But then, just for the
> experiment, I deleted that file and pasted your input in
søn, 2004-04-18 kl. 15:20 skrev Jan Nieuwenhuizen:
> Oddgeir Finstad writes:
>
> > When I ran the file you suggested, it gave me this
> > output - without and with --verbose:
> >
> > 1.
> >
> > [EMAIL PROTECTED] lilypond]$ lilypond kodefiler/test.ly
> > lilypond (GNU LilyPond) 2.2.0
> > Running lil
Oddgeir Finstad writes:
> When I ran the file you suggested, it gave me this
> output - without and with --verbose:
>
> 1.
>
> [EMAIL PROTECTED] lilypond]$ lilypond kodefiler/test.ly
> lilypond (GNU LilyPond) 2.2.0
> Running lilypond-bin...
> Now processing `kodefiler/test.ly'
> Parsing...
>
> /
sÃn, 2004-04-18 kl. 11:21 skrev Jan Nieuwenhuizen:
> Oddgeir Finstad writes:
>
> You may try this:
>
> \header{
> latexpackages="t1enc"
> }
> \score{
> <<
> \notes\relative c' {
> a4 a a a a a a a
> }
> \lyricsto "" \new Lyrics \lyrics {
> \overr
Oddgeir Finstad writes:
You may try this:
\header{
latexpackages="t1enc"
}
\score{
<<
\notes\relative c' {
a4 a a a a a a a
}
\lyricsto "" \new Lyrics \lyrics {
\override LyricText #'font-name = #"ecrb12"
Han f\o -- rer d\o
OK, here is the problem:
\score{
\notes{
\lyrics \new Lyrics {
Her -- ren er min hyr -- de, meg fat -- tes in -- tet.
Her -- ren er min hyr -- de, meg fat -- tes in -- tet.
Han f\o -- rer meg til gr\o n -- ne en
Oddgeir Finstad writes:
> However, when it comes to lyrics, it's more or less game over for me.
> (What I believe to be) standard LaTex encoding only produces a long list
> of error messages.
Best is just to post your .ly file here, include it directly in you mail.
Jan.
--
Jan Nieuwenhuizen <[
On Saturday 17 April 2004 14.21, Oddgeir Finstad wrote:
> An example .ly file with Scandinavian lyrics would probably be the
> easiest way out for me. Or maybe a table with instructions of how to
> type the actual letters? Or some relevant pointers?
>
> Thanks in advance.
>
> Best regards
I have
I'm quite new to LilyPond, very new to this mailing list and not too
proficient with computers in general.
Still I have so far managed to produce a number of scores and
midi-files, mainly for my own practice, and have found solutions to
upcoming problems on the way by searching the documentation.
22 matches
Mail list logo
