<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-15">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-text-html" lang="x-western"> Hello TeXLive
community,<br>
<br>
I'm preparating my first package 'lilyglyphs' for CTAN upload. It
makes notational elements from LilyPond (<a
class="moz-txt-link-freetext" href="http://lilypond.org">http://lilypond.org</a>)
available for continuous text in Lua-/Xe-LaTeX documents.<br>
Unfortunately I have some questions concerning the directory
structure which I absolutely didn't manage to find satisfying
answers for, not even after asking on tex.stackexchange. And also
searching the tex-live archive didn't really make it clear to me.<br>
So I'm sorry to use your time but I have to ask a few questions
(trying to be as concise as possible).<br>
Better now than after a messy upload. I want the package to show
up on CTAN and TeXLive as soon as possible of course ...<br>
<br>
The development repository is at: <a
class="moz-txt-link-freetext"
href="https://github.com/openlilylib/lilyglyphs">https://github.com/openlilylib/lilyglyphs</a>,
and I'm going to write a deploy script to move the files in the
correct places.<br>
The package is rather complex and consists of more than 160 files
currently (with that number growing while the package matures).<br>
<br>
First of all I'm not completely clear about the relation between
the 'plain' directory structure and the supplied tds.zip
structure.<br>
I think the plain lilyglyphs.zip to be downloaded from CTAN can
have mostly the same structure as the development directory. But
it is of course very different from a TDS. <br>
<br>
<br>
a) General questions:<br>
<ul>
<li>Should I write a script that first prepares the whole
directory for CTAN and then copies everything needed to a TDS
structure?<br>
Or should I rather try to make the 'plain' CTAN directory the
same as the TDS structure?<br>
</li>
<li>documentation<br>
Is it better to have the sources and the .pdfs of the
documentation (manual and examples) together in
/doc/lilyglyphs or do the sources go to
/source/lilyglyphs/doc?<br>
</li>
<li>fonts<br>
The package redistributes (unmodified) OpenType font files
under the SIL Open Font License (from <a
class="moz-txt-link-freetext" href="http://lilypond.org">http://lilypond.org</a>).<br>
Do I have to also supply the Metafont sources for these fonts
or is it sufficient to supply a link to the original
developer's Git repository in the FONTLOG?</li>
</ul>
<p>b) TDS related questions:</p>
<ul>
<li>PDFs used by the package<br>
The package uses pdf files in its commands.<br>
These pdfs are generated from LilyPond source files.<br>
The LilyPond source files themselves are generated from
definition files.<br>
In the development directory I have them organized as<br>
/glyphimages<br>
/glyphimages/definitions<br>
/glyphimages/generated_src<br>
/glyphimages/pdfs<br>
I don't really know where to put them. I would place the pdfs
in<br>
/tex/latex/lilyglyphs/glyphimages/pdfs<br>
but I don't know what to do with the rest.</li>
<li>scripts<br>
The package contains a set of Python scripts that help the
user to extend the package<br>
(by generating LaTeX commands from template files and/or by
processing template files to pdf images and generating LaTeX
files)<br>
Of course the user will have to be able to execute them (i.e.
know where they are and have the rights to have them
executable).<br>
I don't know what to do about that. If I put them in
/source/lilyglyphs/py how should I direct the user (in the
manual) so he can make use of these scripts?</li>
<li>The package provides a 'shadow' structure of the above
/glyphimages directory.<br>
If the user wants to extend the package she should copy that
to a location in his private texmf tree and run the scripts in
it (a writable location for extending the package).<br>
Where could I put that in (as a directory structure or an
archive), and how can I refer to that in the manual?</li>
</ul>
<p>Sorry for that long post and number of question.<br>
If I had known that I would probably have developed a simple
package with a .sty and a manual ;-)<br>
</p>
<p>Best wishes and thanks in advance for any clarification<br>
Urs<br>
</p>
</div>
</body>
</html>