On 23-Oct-99 Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
>> On 19-Oct-99 Han-Wen Nienhuys wrote:
>>
>> > from the pavane (no opus number?):
>> >
>> > mutopiacomposer = "Luis Milan (1536-1561)";
>> >
>> > I think that this is not the proper format; that should be L.Milan
>> > (1536-1561). Furthermore, I think it is better not to have the
>> > dates in the mutopiacomposer field. (perhaps a separate field
>> > could be
>> > made):
>> >
>> > In the future it might be necessary to process entries
>> > automatically
>> > if the mutopia headers adhere to a strict format, then directory
>> > names could be easily be destilled from mutopiacomposer and
>> > mutopiaopus.
>>
>> I did think about processing entries automatically but firstly, as
>> you say, the headers need to be in a very strict format, and secondly
>> there is some information that I need for the website that wouldn't
>> be appropriate in the .ly files, eg. size of preview image.
>
> The headers already are in a strict format. But if you like, I can
> make LilyPond output the header to a stricter and more machine
> readable format.
Sorry, I didn't mean that the headers themselves aren't in a strict
format, but that the data contained within the headers would need to be
in a strict format.
eg. mutopiacomposer = the surname of a composer (Capital letter for the
first character, then lower case; excluding any von or van) then a
space followed by his/her initials, each one in capitals (unless it's a
von or van) followed by a full stop. If there are several initials then
spaces need to be put between each one. After these, put the years the
composer was alive in round brackets () showing the full years, eg.
(1810-1854).
Describing each header field in this much detail just starts getting
ridiculous; if I use separate data files then I can easily make sure
every entry is in the same format, as well as including the extra
information that is necessary for each piece of music that wouldn't fit
into the .ly file header (eg. size of preview image, whether multiple
midi files are output, etc.).
Chris
PS. Your patch for LilyPond 1.2.16 on bug-gnu-music fixed my problems as
well - thanks.
--
Chris Sawer - [EMAIL PROTECTED]
