Add \hideNote which is like \hideNotes but just \once.
This still requires translation of an additional sentence
added in Documentation/notation/editorial.itely.
In general, you should not touch the translations. We have translators for that purpose, and ...
13 years, 4 months ago
(2011-11-06 08:42:49 UTC)
#1
In general, you should not touch the translations. We have translators for that
purpose, and they keep track of the original commits corresponding to some
change.
The only exception is when there is a non-compatible syntax change. In that
case, appropriate conversion rules should be added to python/convertrules.py,
and the changes that running scripts/auxiliar/update-with-convert-ly.sh do
should bring the documentation tree into compilable state again, including
translations.
This does not mark the translations as corresponding to a different source
commit, as the human translation is still missing. But that's only your task if
you decide to act as translator, and then you need to do a complete translation,
and do it in the translation branch and update the upstream commit reference.
Issue 5342047: Add \hideNote which is like \hideNotes but just \once.
Created 13 years, 4 months ago by adam.spiers
Modified 13 years, 4 months ago
Reviewers: dak
Base URL:
Comments: 0