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
address@hidden]
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: