Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(9813)

Issue 5342047: Add \hideNote which is like \hideNotes but just \once.

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 5 months ago by adam.spiers
Modified:
12 years, 5 months ago
Reviewers:
dak
CC:
lilypond-devel_gnu.org
Visibility:
Public.

Description

Add \hideNote which is like \hideNotes but just \once. This still requires translation of an additional sentence added in Documentation/notation/editorial.itely.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+72 lines, -34 lines) Patch
M Documentation/changes.tely View 1 chunk +5 lines, -0 lines 0 comments Download
M Documentation/de/notation/editorial.itely View 2 chunks +3 lines, -2 lines 0 comments Download
M Documentation/es/notation/editorial.itely View 2 chunks +3 lines, -2 lines 0 comments Download
M Documentation/es/texidocs/creating-slurs-across-voices.texidoc View 1 chunk +1 line, -1 line 0 comments Download
M Documentation/fr/notation/editorial.itely View 2 chunks +3 lines, -2 lines 0 comments Download
M Documentation/ja/notation/editorial.itely View 2 chunks +3 lines, -2 lines 0 comments Download
M Documentation/notation/editorial.itely View 2 chunks +6 lines, -3 lines 0 comments Download
M Documentation/snippets/contemporary-glissando.ly View 1 chunk +1 line, -2 lines 0 comments Download
M Documentation/snippets/creating-slurs-across-voices.ly View 3 chunks +11 lines, -11 lines 0 comments Download
M Documentation/snippets/new/slides-in-tablature.ly View 1 chunk +2 lines, -4 lines 0 comments Download
M Documentation/snippets/slides-in-tablature.ly View 1 chunk +2 lines, -4 lines 0 comments Download
A input/regression/hide-notes.ly View 1 chunk +21 lines, -0 lines 0 comments Download
M ly/property-init.ly View 2 chunks +11 lines, -1 line 0 comments Download

Messages

Total messages: 1
dak
12 years, 5 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.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b