Re: Corrects links to manuals in many languages (issue 7311074)

[Phil Holmes]

- Original Message - 
From: 

To: 
Cc: ; 
Sent: Wednesday, February 13, 2013 7:01 AM
Subject: Re: Corrects links to manuals in many languages (issue 7311074)




https://codereview.appspot.com/7311074/diff/1/Documentation/cs/web/news-front.itexi
File Documentation/cs/web/news-front.itexi (left):

https://codereview.appspot.com/7311074/diff/1/Documentation/cs/web/news-front.itexi#oldcode11
Documentation/cs/web/news-front.itexi:11: @subsubheading LilyPond
2.13.47 released!  @emph{Jan 28, 2011}
Since news-front.itexi is included in web.itexi, I suspect that deleting
this file would cause the entire build to break.  Did you mean to edit
hu/web.texi as well?


Well...  If news-front isn't in the translation, it's found in the en build 
and used.  Most of the translations work like this.  Except it does cause a 
make website to break, because of the links file which is previously 
created.  Can't remember the exact name.  Locally, I fixed this by nuking 
build and rebuilding from scratch, and all was well.  As it turned out, the 
website build on the server failed for the same reason, so I resorted to 
renaming the build directory on the server and it rebuilt from scratch, so 
all appears OK.



I would rather leave this file alone, or possibly add a "news" item
saying "this translation is out of date".

https://codereview.appspot.com/7311074/diff/1/Documentation/hu/web/basic-authors.itexi
File Documentation/hu/web/basic-authors.itexi (left):

https://codereview.appspot.com/7311074/diff/1/Documentation/hu/web/basic-authors.itexi#oldcode100
Documentation/hu/web/basic-authors.itexi:100: LilyPond Kódrészletek
Tárházának szerkesztője, hibafelelős
woah, why delete this translated file?


It was a very out of date file and not used anywhere in the build.


https://codereview.appspot.com/7311074/


Thanks for the comments.  Appreciated.

BTW - my recent patches have corrected a _lot_ of broken and missing links. 
Prior to this, all of the links on http://lilypond.org/glossary.hu.html were 
broken.  This was true for most of the .hu and .cs docs.  They now all go to 
a page that exists.


--
Phil Holmes 



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Fwd: PATCH: Countdown for 20130215 - 12:00 GMT

[James]

Here is a list of the patches and their current status - next update
20130215.

I thought I'd put all the patches that are now ready for review/in the
countdown and ready to push in the same email.

I am still working out my own personal workflow here (how I format, check,
update etc), so bear with me.

  
3165
Enhancement
d...@gnu.org countdown MultiMeasureTextEvent created by i.e. R1-1 did not
take tweaks  
3163
Enhancement
PhilEHolmes countdown Add Czech translations
3161
Enhancement
mtsolo countdown Standardizes use of empty extents in pure heights and
skylines.  
3134
Enhancement
mtsolo countdown Removes the translate_axis call from axis-group-interface
outside-staff positioning.




 
3174
Enhancement
d...@gnu.org review Add native support of pitched ornamentations
3169
Enhancement
mtsolo review Fixes annotate spacing
3168
Enhancement
d...@gnu.org review Invert the meaning of instrumentTransposition again.
3162
Enhancement
mtsolo review Eliminates pure-print-callbacks list
3160
Defect
mtsolo review cho(rd) names pushed into the staff - Regression




 
3157
Enhancement
d...@gnu.org push Patch: Remove code duplication for cue clefs
3034
Documentation
d...@gnu.org push DOC: Thumb but also "finger changes" should be Fingering
1863
Defect
d...@gnu.org push Explicit fingering direction (^3) has no effect if
Fingering#'direction is set
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Issue 3174: Implement \accidental markup and \pitched command for transposable accidental markups (issue 7323060)

[tdanielsmusic]

I definitely prefer the alternative you suggest in para 3.
You would not then need the warning, which is only necessary due to the
complicated 2-stage interface.


https://codereview.appspot.com/7323060/diff/1/scm/define-markup-commands.scm
File scm/define-markup-commands.scm (right):

https://codereview.appspot.com/7323060/diff/1/scm/define-markup-commands.scm#newcode2777
scm/define-markup-commands.scm:2777: (ly:warning (_ "No pitch found.
Have you forgot \\pitched?"))
Did you forget ...

https://codereview.appspot.com/7323060/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Issue 3174: Implement \accidental markup and \pitched command for transposable accidental markups (issue 7323060)

[thomasmorley65]

On 2013/02/13 22:56:30, Trevor Daniels wrote:

I definitely prefer the alternative you suggest in para 3.
You would not then need the warning, which is only necessary due to

the

complicated 2-stage interface.


I'd second.

Regarding:

melody =
\relative c' {
%\override Script #'script-priority = #-100
%\override TextScript #'script-priority = #100
\key c\major
c2^\trill^\pitched des
  -\markup
 \accidental
d!
c2^\prallprall^\pitched des
  -\markup  % \fontsize #-6 \translate #'(0.6 . 0)
 \accidental
d!
}
\new Staff { \melody }
\new Staff { \transpose c' e' \melody }

Without the commented commands, TextScript and Script are switching
their positions and aren't well aligned (worse while using \prallprall).

Rather a matter of documentation/example.

https://codereview.appspot.com/7323060/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel