Re: Subject: Re: lilyglyphs LaTeX package

2012-08-16 Thread Urs Liska

Now I know that, thanks :-)

Just had to exclude this from the git repo that controls my texmf dir ;-)

Best
Urs

Am 16.08.2012 14:29, schrieb Werner LEMBERG:

~/texmf/tex/xelatex/lilyglyphs/

Oops, didn't think this would work with the subfolder ...

This gets searched recursively by default.


Werner

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Subject: Re: lilyglyphs LaTeX package

2012-08-16 Thread Werner LEMBERG

>>~/texmf/tex/xelatex/lilyglyphs/
> Oops, didn't think this would work with the subfolder ...

This gets searched recursively by default.


   Werner

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Subject: Re: lilyglyphs LaTeX package

2012-08-16 Thread Urs Liska

Am 16.08.2012 13:57, schrieb Werner LEMBERG:

  * place lilyglyphs.sty and the complete definitions/ folder somewhere
on your disk, e.g. in a directory ~/lilyglyphs.
  * create symlinks to lilyglyphs.sty and the definitions/ folder _in
the directory_ where your .tex file is located:
ln -s ~/lilyglyphs/lilyglyphs.sty
ln -s ~/lilyglyphs/definitions
-> This is going to pretend that the package is in the same dir as
your .tex file.
Alternatively you can (for testing the package) put your .tex file
in the directory where lilyglyphs.sty is.

Ouch.  Why not simply put it into your local TEXMF folder, usually
~/texmf?  Then you don't have to do any further links!  If it doesn't
exist yet, you should create it.  An appropiate subdirectory is

   ~/texmf/tex/xelatex/lilyglyphs/

Oops, didn't think this would work with the subfolder ...


 Werner

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Subject: Re: lilyglyphs LaTeX package

2012-08-16 Thread Werner LEMBERG
>  * place lilyglyphs.sty and the complete definitions/ folder somewhere
>on your disk, e.g. in a directory ~/lilyglyphs.
>  * create symlinks to lilyglyphs.sty and the definitions/ folder _in
>the directory_ where your .tex file is located:
>ln -s ~/lilyglyphs/lilyglyphs.sty
>ln -s ~/lilyglyphs/definitions
>-> This is going to pretend that the package is in the same dir as
>your .tex file.
>Alternatively you can (for testing the package) put your .tex file
>in the directory where lilyglyphs.sty is.

Ouch.  Why not simply put it into your local TEXMF folder, usually
~/texmf?  Then you don't have to do any further links!  If it doesn't
exist yet, you should create it.  An appropiate subdirectory is

  ~/texmf/tex/xelatex/lilyglyphs/


Werner

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Subject: Re: lilyglyphs LaTeX package

2012-08-16 Thread Urs Liska
The package doesn't have real installation instructions (or even an 
installation procedure) yet (something for 0.1, a first official release).


Fortunately xelatex-ubuntu is what I have, so I can tell you how you 
will make it work.


One issue is that there are included files in a subfolder. (I assume 
I'll have to do something about that for a 'real' packaged version.)


As a dirty quick 'installation' I recommend:

 * place lilyglyphs.sty and the complete definitions/ folder somewhere
   on your disk, e.g. in a directory ~/lilyglyphs.
 * place the Emmentaler OTF file from the OTF folder in ~/.fonts
   (Maybe you have to run "fc-cache" afterwards to update your
   fontconfig cache - but I don't know for sure, I can't do any harm
   anyway)
 * create symlinks to lilyglyphs.sty and the definitions/ folder _in
   the directory_ where your .tex file is located:
   ln -s ~/lilyglyphs/lilyglyphs.sty
   ln -s ~/lilyglyphs/definitions
   -> This is going to pretend that the package is in the same dir as
   your .tex file.
   Alternatively you can (for testing the package) put your .tex file
   in the directory where lilyglyphs.sty is.

You may get  long lists of 'kpathsea' errors. This is what I had on some 
of my computers (not only with this package but also earlier with other 
OpenType fonts and fontspec). I finally found out that this happened 
when I had 'activated' the respective fonts with a font manager 
(FontMatrix). When all these references were away, fontspec worked fine.


Hope this helps (works)
Best
Urs


Am 16.08.2012 13:37, schrieb Stefan Thomas:

Dear Urs,
how can I install this package in my xelatex-system on ubuntu?


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Subject: Re: lilyglyphs LaTeX package

2012-08-16 Thread Stefan Thomas
Dear Urs,
how can I install this package in my xelatex-system on ubuntu?

Hi Reinhold, Werner and Philippe,

thanks for your feedback. Here are a few ideas before I finally leave.
[I won't read this list (from tomorrow), so if you want to contact me in
the next weeks, please write to g...@ursliska.de]

My package works with XeLaTeX because I decided to use this flavor.
Actually the possibility to access OpenType fonts and features that way
was the final point for my decision to seriously jump into LaTeX use.

As Philippe and Werner pointed out there are ways to use Emmentaler
glyphs also in plain LaTeX, but I won't actively go after this.

What I propose, and what I think is quite possible, is:

  * There is the generic access command (\lilyGlyph ATM)
  * This command is then called by the predefined commands (such as e.g.
\doublesharp) and can be called within a LaTeX document.
  * If we can manage to keep the interface to this generic command
consistent I would be happy to include another 'backend'.
  * I think that the generic access command could become rather an
'interface' command. Depending on an option that can be passed to
the package, the interface command would then call the appropriate
generic access command.
  * Maybe it's necessary to somehow create a lookup table to map the
Type1 numbers to the OpenType glyphnames. I found this for example:

https://groups.google.com/forum/?fromgroups#!topic/comp.text.tex/MDzy2xNUC84[1-25]
- which could be of help.
  * If that works, everything that comes at a higher level (i.e. the
actual glyph commands) could be independent of the used LaTeX flavor.

This has a few consequences:

  * There will be the need for more discussion and design before my
prospected first official '0.1' release - but I think it would be
worth the time and effort.
  * I won't be able to add new glyphs before this design phase is
finished (because I'm afraid of having to update all the commands
due to changed syntax). This is principally OK with me, but could
cause some headaches because I started all this for a current
project - and I think this revision report will be quite long, and I
need the glyphs for it ...
  * I probably won't / can't do anything about the 'plain LaTeX backend'
- just because I don't know anything about it, and I can't afford
the time developing something I won't ever use myself.
  * ATM the stuff of integrating two 'backends' through package options
seems over my head (as I'm practically new to LaTeX). Maybe I will
learn it on the way, but any assistance in this field would be
appreciated.

Best for now
Urs

Am 15.08.2012 17:34, schrieb Urs Liska:
> Hi list,
>
> this is somewhat OT, but only slightly, I think.
> In need to insert music glyphs in continuous text (for writing a
> revision report) I successfully found out how to insert glyphs from
> LilyPond's Emmentaler font in (Xe)LaTeX documents and wrote a few
> first commands (thanks to Google and Werner Lemberg).
>
> As this may well be useful for anybody writing about music with LaTeX,
> I decided to make a package out of it. The project is hosted at
> https://github.com/uliska/lilyglyphs.
>
> The package is already useable, but there will be some syntax changes
> in the near future, so I'd rather not use it extensively (you can see
> the issues in the tracker to get an impression).
>
> For now there are a few predefined commands for glyphs, and a generic
> command to access glyphs by their name, so anything should already be
> possible.
>
> In the download section there is a pdf that documents how it works so
> far and also gives a good impression on what it looks like.
> You may either clone into the repository or download the package
> archive from the download page. So far there aren't any useful
> installation instructions, but I think it should work. You can place a
> symlink to the .sty file and a symlink to the definitions/ directory
> in the directory of your .tex file, and it should work.
>
> I will be away for two weeks but would be happy to find a few
> collaborators afterwards to join the project.
> a) there are a few issues that I would prefer not to decide alone but
> rather discuss,
> b) a few issues with LaTeX programming where I'd appreciate some help,
> and
> c) the ultimate goal is to cover the whole glyph set, but this will
> only become reality with several contributors. I will happily work on
> glyphs that I use personally, but there are so many things I won't use
> ...
>
> I hope this is on interest to anybody. Please feel free to forward
> this message to whom it may concern ...
>
> Best
> Urs
>
> __
_
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user