On Sat, Apr 10, 2010 at 12:02 PM, Graham Percival
wrote:
> On Sat, Apr 10, 2010 at 08:19:50PM +0200, Jan Nieuwenhuizen wrote:
>> The past few weeks I looked at what is holding up the new website.
>
> - still some CSS issues.
Would it be worth trying to recruit someone to work on the CSS again?
I
Oops. Too slight errors in the previous post's attachment:
61c61
< c) is downstem
---
> c) is upstem
76,77c76,78
< run is a second, and neither note is on the middle line, then
< move on (no adjustment is needed in this case).
---
> run is a second, and neither note
2010/4/11 John Mandereau :
> Il giorno sab, 10/04/2010 alle 14.32 +0200, Jan Nieuwenhuizen ha
> scritto:
>> And then there are comment entries from inline
>> .ly file, such as
>>
>> #. Documentation/learning/tutorial.itely:256 (comment)
>> msgid "c is 1 staff space up, so is the c above"
>> msgstr
Hi Jan,
Il giorno sab, 10/04/2010 alle 20.19 +0200, Jan Nieuwenhuizen ha
scritto:
> Yesterday I fixed a texi2html node translation problem, skeleton
> files (untranslated files with most only @untranslated markers)
> are no longer necessary.
>
> I have fixed scripts/build/website_post.py and today
Il giorno sab, 10/04/2010 alle 14.32 +0200, Jan Nieuwenhuizen ha
scritto:
> And then there are comment entries from inline
> .ly file, such as
>
> #. Documentation/learning/tutorial.itely:256 (comment)
> msgid "c is 1 staff space up, so is the c above"
> msgstr ""
>
> #. Documentation/learning/tu
2010/4/10 Jan Nieuwenhuizen :
> Op zaterdag 10-04-2010 om 17:33 uur [tijdzone +0200], schreef Francisco
> Vila:
>
>> This makes comments inside lilypond blocks to be magically translated.
>
> Yes, and we need that extra magic why exactly?
I think John implemented this to achieve coherent translati
On Sat, Apr 10, 2010 at 08:19:50PM +0200, Jan Nieuwenhuizen wrote:
> The past few weeks I looked at what is holding up the new website.
Other issues are:
- need a redesign/rethink of introduction. That's pending me
looking at stuff and making some decisions.
- some manual links in the "stable"
For what it's worth, I figured out an algorithm for
improving the stem lengths, to accommodate making
adjustments dynamically, according to the guidelines set
forth by Ted Ross. I don't know if anyone cares to do this
right now, but I might as well post it in case someone
eventually wants to.
Thi
Hi,
The past few weeks I looked at what is holding up the new website.
For starters, I did a translation of [1] and [2] deliveries for
the dutch website [nl].
Yesterday I fixed a texi2html node translation problem, skeleton
files (untranslated files with most only @untranslated markers)
are no l
Op zaterdag 10-04-2010 om 18:23 uur [tijdzone +0200], schreef
Jean-Charles Malahieude:
> It would effectively be nice if the parsing that generates the "pot"
> file to exclude the translation-subdirs...
I agree this is truly silly -- done.
> But this fr.po file is very useful to me:
> when I en
Op zaterdag 10-04-2010 om 17:33 uur [tijdzone +0200], schreef Francisco
Vila:
> This makes comments inside lilypond blocks to be magically translated.
Yes, and we need that extra magic why exactly?
I can imagine we want it for lsr snippets, but for .ly in the docs,
isn't it much easier for trans
Le 10/04/2010 14:28, Jan Nieuwenhuizen disait :
Hi John,
I fixed make -C Documentation po-update which has
been broken for quite some time now. However, there
are a couple of things that I cannot fix, as I do
not understand what it's for.
Can you please have a look at my questions in commit
8
2010/4/10 Jan Nieuwenhuizen :
> Hi John,
>
> I fixed make -C Documentation po-update which has
> been broken for quite some time now. However, there
> are a couple of things that I cannot fix, as I do
> not understand what it's for.
>
> Can you please have a look at my questions in commit
> 858e50
2010/4/10 Jan Nieuwenhuizen :
> Op zaterdag 10-04-2010 om 14:28 uur [tijdzone +0200], schreef Jan
> Nieuwenhuizen:
>
>> The .po files in Documentation/po are /huge/ and I
>> esp. do not understand why they have @node names
>> in them, and not only english ones.
>
> And then there are comment entrie
Op zaterdag 10-04-2010 om 14:28 uur [tijdzone +0200], schreef Jan
Nieuwenhuizen:
> The .po files in Documentation/po are /huge/ and I
> esp. do not understand why they have @node names
> in them, and not only english ones.
And then there are comment entries from inline
.ly file, such as
#. Docum
Hi John,
I fixed make -C Documentation po-update which has
been broken for quite some time now. However, there
are a couple of things that I cannot fix, as I do
not understand what it's for.
Can you please have a look at my questions in commit
858e506, ie
http://git.savannah.gnu.org/gitweb/?p=l
On 4/10/10 2:08 AM, "Mark Polesky" wrote:
> Carl Sorensen wrote:
>> As I read Ross, the 1/4 staff-space adjustment is what one
>> would use if in the midst of a note cluster (perhaps
>> limited to a measure according to the text explaining
>> Example 1 and Example 2) that contains the a, b, c
Thanks for all your help. Find attached a third version of my patch for
syllables under grace notes. Compared to the patch dated March 31, the
following has been done:
* 2 regression tests added (a basic test and a lyric extender test),
* different wording in the docs (according to the hints by
On Wed, Apr 07, 2010 at 09:22:09AM +0200, Carsten Steger wrote:
> Xaiver, Graham,
>
> On Tue, Apr 6, 2010 at 10:11 AM, Xavier Scheuer wrote:
> > On 5 April 2010 12:19, Graham Percival wrote:
> >> An example of this is in LSR. Try searching for "jazz tempo" or
> >> something ilke that.
> >
> > R
Op zaterdag 10-04-2010 om 10:49 uur [tijdzone +0200], schreef
Jean-Charles Malahieude:
> Just one question:
> is it intentional to suffix everything with"-es" in every language in
> your commits
> "Doc: [LANG] Append -LANG to weblink macros. Fixes web link translations."
> or just skating on the
Le 10/04/2010 08:15, Jan Nieuwenhuizen disait :
Op vrijdag 09-04-2010 om 23:20 uur [tijdzone +0200], schreef
Jean-Charles Malahieude:
Good catch!
Corrected, tested (OK) and pushed.
Thanks! I clarified the need for these two strings to help
other translators.
Just one question:
is it int
Carl Sorensen wrote:
> As I read Ross, the 1/4 staff-space adjustment is what one
> would use if in the midst of a note cluster (perhaps
> limited to a measure according to the text explaining
> Example 1 and Example 2) that contains the a, b, c, and
> d, so we need to keep the stem progression mo
22 matches
Mail list logo
