[EMAIL PROTECTED] writes:
>
> > I've put the first component of TeX generated text metrics in place
> > [...]
> >
> > as you can see, I used a lispish format for now. The format is :
> >
> > (FONT-NAME MAGNIFICATION TEXT)
>
> After some investigation I found out that you have to do ugly hacks to
> convert a Lisp string to a TeX argument. The main reason is that
> after reading an input line the catcodes in TeX are fixed and can't be
> changed again. I had to use an auxiliary file to write the converted
> strings, then reading them again -- etex has a new operator to avoid
> that but we can't assume that etex is used everywhere...
>
> > If you can define a standard format for TeX input, write macros for
> > dimension handling, and provide a TeX output like
> >
> > (FONT-NAME MAGNIFICATION TEXT BBOX-LIST)
>
> For the same reasons, it is not possible to repeat the input argument
> in the output without using an auxiliary file. I thus decided to use
> the following input format which isn't lispish any more but which
> should be easy to generate:
Hi,
I've put some preliminary code in CVS. use with
lilypond -f texstr foo
latex foo.texstr
add
#(ly:load-text-dimensions (eval-string (format "(quote (~a))"
(ly:gulp-file "foo.lpm"))
))
to the .ly, and run.
I'm not sure that this yields the correct result, but the dimensions
seem to be used by lily.
Note: this code expects the numbers to be in points.
TODO:
* verify results
* add code to load the .lpm file automatically
* add code to make lilypond-book do two passes to generate and
use .lpm
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
