On Sat, Jul 19, 2008 at 7:58 PM, Graham Breed <[EMAIL PROTECTED]> wrote:
>> (define-public (layout-set-absolute-staff-size-in-module module
>> staff-height)
>>
>> this sets a variable 'fonts, which is a Font-tree-element (see
>> scm/font.scm), a tree defining how to select a font using font-shape,
Han-Wen Nienhuys wrote:
Looking a bit more into this, the memories of why this is so
complicated come back.
In paper.scm, the default fonts are setup in
(define-public (layout-set-absolute-staff-size-in-module module staff-height)
this sets a variable 'fonts, which is a Font-tree-element (see
On 2008/07/19 21:19 +0200, Reinhold Kainhofer wrote:
> Okay, I've now added the script buildscripts/extract_texi_filenames.py to
> create that list (tab-separated file with entries
> NODENAME\tFILENAME\tANCHORNAME). I took the texi-gettext.py file and adjusted
> it (basically rewrote everything,
2008/7/19 Valentin Villenave <[EMAIL PROTECTED]>:
> 2008/7/19 Francisco Vila <[EMAIL PROTECTED]>:
>> For example, the down-arrow as a mark in
>> http://lsr.dsi.unimi.it/LSR/Item?id=433
>> "Aligning marks with various notation objects"
>> it is in NR1.8.1.3 Text marks,
>
> My bad; I put this glyph
On Sat, 19 Jul 2008 18:11:31 +0200
John Mandereau <[EMAIL PROTECTED]> wrote:
> On 2008/07/19 17:13 +0200, Reinhold Kainhofer wrote:
> > > I generally agree about not hurrying too much. I vote for merging
> > > dev/texi2html into master as soon as the docs look good enough:
> > > no or very few br
2008/7/19 Francisco Vila <[EMAIL PROTECTED]>:
> For example, the down-arrow as a mark in
> http://lsr.dsi.unimi.it/LSR/Item?id=433
> "Aligning marks with various notation objects"
> it is in NR1.8.1.3 Text marks,
My bad; I put this glyph because it clearly emphasized the horizontal
alignment (whi
> For example, the down-arrow as a mark in
> http://lsr.dsi.unimi.it/LSR/Item?id=433
texinfo doesn't provide a definition for U+2193 because it doesn't
define \downarrow. However, this is defined in plain TeX, thus
adding something like
@tex
\DeclareUnicodeCharacter{2193}{\downarrow}
@end
Looking a bit more into this, the memories of why this is so
complicated come back.
In paper.scm, the default fonts are setup in
(define-public (layout-set-absolute-staff-size-in-module module staff-height)
this sets a variable 'fonts, which is a Font-tree-element (see
scm/font.scm), a tree defi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 19. Juli 2008 schrieb John Mandereau:
> > - -) decide how to modify the build process to use the
> > secname->filename/anchor map. We can either run texi2html twice on all
> > files (run it once on all files and only after that we can run i
Han-Wen Nienhuys wrote:
Ah, ok. The problem is that the Pango font is 'virtual': pango
decomposes the string into sections each of which can use a different
font.
Oh, it is? What do we do about it?
I found this in a file which I did get to work (in the sense
of producing Sagittal symbols, n
Ah, ok. The problem is that the Pango font is 'virtual': pango
decomposes the string into sections each of which can use a different
font.
On Sat, Jul 19, 2008 at 10:51 AM, Graham Breed <[EMAIL PROTECTED]> wrote:
> Han-Wen Nienhuys wrote:
>>
>> On Thu, Jul 17, 2008 at 11:10 AM, Graham Breed <[EMA
2008/7/19 John Mandereau <[EMAIL PROTECTED]>:
>> Hmm, I thought the German and Spanish translations are basically complete
>> (maybe not right now for GDP, but at least for the latest released version)
>
> Spanish translation of LM is actually the only complete translation, so
> I should have a loo
For example, the down-arrow as a mark in http://lsr.dsi.unimi.it/LSR/Item?id=433
"Aligning marks with various notation objects"
it is in NR1.8.1.3 Text marks,
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Text-marks.html
HTML is OK, but PDF shows the code verbatim and the mark string is
> > Which characters are we talking about?
>
> Characters in cyrillic, Hebrew and Japanese alphabets in
> input/{lsr,regression}/utf-8.ly.
OK, this won't work with texinfo's PDF output. This particular file
should get a proper warning, or perhaps the makefiles can be adjusted
not to process this
On 2008/07/19 17:13 +0200, Reinhold Kainhofer wrote:
> The big disadvantage of using an external script to generate the file names
> is
> that I basically have to duplicate the code (for generating the file name and
> deciding into which files to put the subsections) that is also in the
> texi2
On 2008/07/19 17:35 +0200, Werner LEMBERG wrote:
> > BTW it's not LaTeX, it's texinfo.tex powered by TeX, which has no
> > support for non-European languages AFAIK. Well, to be brief, this
> > issue is postponed.
>
> Which characters are we talking about?
Characters in cyrillic, Hebrew and Japan
> BTW it's not LaTeX, it's texinfo.tex powered by TeX, which has no
> support for non-European languages AFAIK. Well, to be brief, this
> issue is postponed.
Which characters are we talking about?
Werner
___
lilypond-devel mailing list
lilypond
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 19. Juli 2008 schrieb John Mandereau:
> On 2008/07/18 01:24 +0200, Reinhold Kainhofer wrote:
> > - -) decide how to modify the build process to use the
> > secname->filename/anchor map. We can either run texi2html twice on all
> > files (ru
On 2008/07/19 16:50 +0200, Francisco Vila wrote:
> Are you aware that LSR encourages to use special utf-8 characters but
> Latex is unable to show them in the verbatim code of the snippets on
> PDF docs?
Yep, this wasn't a problem when this snippet was only in regtests, but
now we're embarrassed.
> Are you aware that LSR encourages to use special utf-8 characters
> but Latex is unable to show them in the verbatim code of the
> snippets on PDF docs?
This can be configured, for example by properly using Babel to switch
between languages.
Werner
___
Are you aware that LSR encourages to use special utf-8 characters but
Latex is unable to show them in the verbatim code of the snippets on
PDF docs?
2008/7/19 Francisco Vila <[EMAIL PROTECTED]>:
> IMO the PDF format is perfect as a single-file solution, as easily
> searchable as the bigpage HTML,
2008/7/19 John Mandereau <[EMAIL PROTECTED]>:
> It's correct; only fully translated manuals should be compiled in a
> single page format, because partially translated manuals are sort of a
> mess with a long succession of empty sections in single page format, a
> bit like PDF format -- but PDF outp
On 2008/07/18 01:24 +0200, Reinhold Kainhofer wrote:
> Just today, I started implementing the sectionname<=>filename map (which
> needs
> to be written out to a file on disk, so that external refs from other manuals
> can load this and look up the correct file/anchor to point to). I'm already
>
Han-Wen Nienhuys wrote:
On Thu, Jul 17, 2008 at 11:10 AM, Graham Breed <[EMAIL PROTECTED]> wrote:
\override Accidental #'font-name = #"Sagittal"
in a script, and characters from Accidental's glyph-name-alist can come from
Sagittal. The problem is that LilyPond can't retrieve named glyphs
On Sat, 19 Jul 2008 00:35:26 +0200
John Mandereau <[EMAIL PROTECTED]> wrote:
> On 2008/07/18 00:12 -0700, Graham Percival wrote:
> > Minor proofreading is easily done after 2.12. Also, it can be
> > done by normal users. I really want texi2html to be working for
> > 2.12, and you two are the onl
On Fri, 18 Jul 2008 17:52:32 +0100
"Neil Puttock" <[EMAIL PROTECTED]> wrote:
> 2008/7/18 Graham Percival <[EMAIL PROTECTED]>:
>
> >> Will do, though I don't plan on removing ragged-right = ##t for the
> >> remaining items.
> >
> > All right, I'll do it after you revert the time signature stuff.
>
26 matches
Mail list logo
