Christopher Antila
2011-01-14 05:47:04 UTC
Hello:
I don't know if anybody else has started to think about Google Summer of
Code yet, or if anybody is watching this list yet, but I have an idea!
I would like to write documentation for LaTeX and various extensions
that might be used for scholarly musical research. This would primarily
involve LaTeX itself, the extensions required to run the
biblatex-chicago pacakge, and the commands and procedures required to
integrate LilyPond-generated musical scores.
Although the above-listed components already have well-written
documentation, learning how to use the software takes a significant
amount of effort, experimentation, and sifting. What makes this document
unique from other existing documentation is, essentially, its
single-mindedness. The target audience would be music scholars and
students, but I would be careful to write certain sections so they are
useful to anybody who uses the Chicago Manual of Style.
If the TUG would welcome use-case-specific documentation, I will be
happy to provide more information on the scope of the envisioned
project, and my previous experience.
Regards,
Christopher Antila.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://tug.org/pipermail/summer-of-code/attachments/20110114/2479b3cb/attachment.bin>
I don't know if anybody else has started to think about Google Summer of
Code yet, or if anybody is watching this list yet, but I have an idea!
I would like to write documentation for LaTeX and various extensions
that might be used for scholarly musical research. This would primarily
involve LaTeX itself, the extensions required to run the
biblatex-chicago pacakge, and the commands and procedures required to
integrate LilyPond-generated musical scores.
Although the above-listed components already have well-written
documentation, learning how to use the software takes a significant
amount of effort, experimentation, and sifting. What makes this document
unique from other existing documentation is, essentially, its
single-mindedness. The target audience would be music scholars and
students, but I would be careful to write certain sections so they are
useful to anybody who uses the Chicago Manual of Style.
If the TUG would welcome use-case-specific documentation, I will be
happy to provide more information on the scope of the envisioned
project, and my previous experience.
Regards,
Christopher Antila.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://tug.org/pipermail/summer-of-code/attachments/20110114/2479b3cb/attachment.bin>