Re: mixing hebrew and english in latex

[Aaron]

Thanks I am just not sure where to tell lilypond to use babel or ivritex
etc.

When I add it to the start of the lyrics
with a doubled backslash as per lilypond I get the command in english in
the resulting dvi or ps.

\\hebalef
under the staff.
I was told to double the \\ and quote the foriegn language words when
using latex in lilypond.

I get no complaints if I double the \\ but no hebrew. I must be able to
tell Lilypond to use ivritex or bable etc when processing the latex???

At the beginning of the file it complains in the lyrics no hebrew???

Thanks

I really appreciate the help and any other ideas will be most welcome.
Aaron
On Fri, 2003-06-20 at 17:41, Tzafrir Cohen wrote:
> On Thu, Jun 19, 2003 at 08:55:28PM +0300, Aaron wrote:
> > The letter I got was from lilypond list and from what I remember you can
> > add both Tex and Latex within lilypond.
> > 
> > And yes there is no musixtex in lilypond.
> > 
> > but how do I do it???
> 
> I took anther look yesterday. Still no luck. Still, the following
> observations:
> 
> * lilypond produces what seems to be plain tex, and is latex processed
>   to the command 'tex'
> 
> * If you use 'lilypond -f ps' or similar yu should probably use etex
>   instead of tex. Try setting the env. var TEX to 'etex' . e.g: (in
>   bash):
> 
>     TEX=etex lilypond -f ps file.ly
>   
>   (untested)
> 
> * To add the standard Hebrew support for LaTeX2e you can use
>   'latexpackages' and 'latexoptions' in the header
> 
> \header{
>   [snip]
>     latexpackages = "babel"
>     latexoptions  =  "hebrew,english"
> }
> 
> 
> * Both "ivritex" and "lilypond" make extensive use input decoding (the
>   class inputenc). The char is immediately interpettted to a macro.
>   I'm not exactly sure how to make inputenc work with both. 
> 
>   So for starters work with \hebalef , \hebbet etc. instead of the real
>   Hebrew letters.
> 
> * But even with that, I couldn't find the place to put some uninterperted
>   latex macros. lilypond always shouted it couldn't recognise \R{},
>   \hebalef, and such.