David Stone a écrit : > May I make a plea for these to be recognised as problems which ideally > should be solved? > > I know it is possible to work round most of them by adding a (z) in > the gabc, but there are times when this is difficult. I am thinking > in particular of gabc files which have in turn been generated by > another program. (I have myself written a program which expands > pointed psalms so that they are fully written out, for easier reading > by those unfamiliar with pointing. Currently this outputs Lilypond, > but gabc would be better.) > > I am willing to raise the bug reports and write test cases > demonstrating the problem. I don't think I have deep enough knowledge > of TeX to fix them, I'm sorry to say. >
No problem. Do not hesitate to fill bugs (https://gna.org/bugs/?group=gregorio) or tasks (https://gna.org/task/?group=gregorio) on the bugtracker of gregorio. > Those I have noticed are: > > - sometimes if the last real staff is full, it is followed by an empty > staff. > This can be considered as a bug... I think I can fix it, or at least make it happen less often. With LuaLaTeX it would be possible to totally eradicate it, as well as some empty staff appearing after forced line breaks. > - in the same case, a staff has a spurious custos, even though there > are no more notes. > This is exactly the same bug as the previous one, if you fix the previous, you'll fix this one. > - there is sometimes insufficient space between the clef and the first > note of the line, especially if the first syllable on the line > starts with a vowel. (The Antiphonale Monasticum of 1934 seems to > leave a space of about 1.5 notehead widths, at least.) > This space is adjusted if you put a z, but I'll try to find a solution for the case where you don't set z manually. You can report it as a bug. > - the alternative form of divisio finalis, two vertical lines at the > very end of the staff (rather than a little before the end) can at > present only be chosen manually by editing the gregoriotex file. It > would be better if this was done automatically at the end of a > piece when the line is full. > You can report it as a taks, as this bug is only solvable in LuaLaTeX, at least I think so... If someone is an expert in .aux files, would it be possible with an aux file? I'm waiting for texlive 2008 to reach debian/sid to work on it. But not everyone has a working LuaLaTeX... > - currently a divisio can appear at the start of a line. It would be > better if line breaks never occurred just before a divisio. > This seems almost unfixable, but maybe it's not, you can report it as a bug... > - Sometimes, if a word is broken across a line boundary, there is no > hyphen. There should be a hyphen. > Same thing as above with LuaTeX. Actually the code for LuaLaTeX is already written. > - it does not seem possible to have a key signature of a single B > flat. This would be useful for some late chants of mode V or mode > VI, which are really major. Perhaps this is not part of the core > chant notation, but it is used occasionally with English adaptions. > (For example, the `Plainchant Gradual' (English) uses a Bb key > signature for the Gradual Blessed art thou, Benedictus es, of > Trinity Sunday, although the Liber Usualis writes every Bb with its > own flat sign for the melody.) > You can report it as a task. > - It would also be useful if the relevant TeX parameters were > mentioned in the documentation, especially if their use is different > (is it?) from their use with ordinary tex. I have had some success > at adjusting the line breaks in gregoriotex output by changing > \tolerance. > Actually I don't really understand. I've never changed any TeX parameter, and I don't think it should be necessary, but I never explored this way... what kind of value is good? _______________________________________________ Gregorio-devel mailing list [email protected] https://mail.gna.org/listinfo/gregorio-devel
