| Re: [translations] Commas in doctitle string |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: John Mandereau <john.mandereau@xxxxxxxxx>
- Subject: Re: [translations] Commas in doctitle string
- From: Francisco Vila <paconet.org@xxxxxxxxx>
- Date: Thu, 4 Feb 2010 12:18:50 +0100
- Cc: translations <translations@xxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Pri0WpWc7zb8XG4/3ILvFSGzFfwdzW9nE3Nv07lGGH4=; b=E0hg2aALufD1rHH+dcGkrGw/jstOiT01f/OOTE7H//HAxyOG3zyOXD26QvqOXg62FQ Az1Yk2mGuZGLamILQwNnC4TjeI7pTH633WZyul9HJjXeQZFs25DFQ4yYbgss/R917MsJ zX0D9X3zfZiOYjFTTsXy0ASnlVtJG08YnNsGk=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=uPtnW6kJTsYFujCkQzLWliKQnbJfH/00iaW/ndNWU2lggKoFnYupmmzVkCUvCB4PLN oVVYKZEsM44+Ix0SWxqsi1rSXHuYfTfY7yCYHfi63BPvvEQMzmGCksnqMnPoR/AB/MUN UfkKTuHxwzfHFpbBE40YTip6tY5aoT3CTYL0Q=
2010/2/4 John Mandereau <john.mandereau@xxxxxxxxx>:
> Hi Francisco,
> Le jeudi 04 février 2010 à 11:49 +0100, Francisco Vila a écrit :
>> Aren't commas allowed in doctitle strings? I was not aware. See
>>
>> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blobdiff;f=Documentation/snippets/adding-beams%2C-slurs%2C-ties-etc.-when-using-tuplet-and-non-tuplet-rhythms.ly;h=9fb7fe9fcb05a33ea55d1386bdfe5302470309ef;hp=28146c12f7df4a671b0c1c8d1a2c86d4f4180f2c;hb=d069aeb6109be7dd0f93b1e6b65f79198335ab96;hpb=11af64cf957f71ba2d9251fae30882f6743eff10
>>
>> or commit d069aeb6109be7dd0f93b1e6b65f79198335ab96 . Did makelsr
>> remove the commas?
>
> Indeed, makelsr.py removes the commas because the doctitle is used as a
> Texinfo node name, in which commas and other characters are forbidden --
> please see Texinfo manual for more details.
Thank you. I don't like commas supressed from the resulting PDF or HTML, though.
One more question: after having updated our files in
texidocs/*.texidoc do we still have to make makelsr and commit the
result?
Thanks!
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com