Windows Start Menu Shortcuts need updating
If I select Start Menu Shortcuts when I install LP 2.11.65-1 on my Windows XP,I get the following 6 shortcuts: 1. Examples 2. LilyPond Tutorial 3. LilyPond Website 4. Music in Mutopia 5. Uninstall 6. LilyPond Shortcut 1. (Examples) points to a non-existent file: \LilyPond\usr\share\doc\lilypond-2.11.65-1\input This causes Windows to start searching for the file with the following message: Missing Shortcut: Windows is searching for input. To locate the file yourself, click Browse. This makes a poor first impression... Shortcut 2. (LilyPond Tutorial) points to an old link http://lilypond.org/tutorial which redirects to a version 2.10 doc page! http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Tutorial.html Instead it should point here, I presume: http://lilypond.org/doc/v2.11/Documentation/user/lilypond-learning/Tutorial Looking forward to finally seeing 2.12! - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Fwd: one big page refers to itself
Hello, I've fixed and tested this in html NR. Looks good? Please
suggest a possibly better string for the not-single-big-page link. If
it is OK, I'll apply it to the three manuals in all languages. I've
not touched the PDF.
diff --git a/Documentation/user/lilypond.tely b/Documentation/user/lilypond.tely
index 850e2a8..0dce93a 100644
--- a/Documentation/user/lilypond.tely
+++ b/Documentation/user/lilypond.tely
@@ -68,9 +68,16 @@ Distributions will want to install lilypond.info in
postinstall, doing:
@ifhtml
[EMAIL PROTECTED] bigpage
This document is also available as a
@uref{source/Documentation/user/lilypond.pdf,PDF} and as
@uref{source/Documentation/user/lilypond-big-page.html,one big page}.
[EMAIL PROTECTED] ifclear
[EMAIL PROTECTED] bigpage
+This document is also available as a
[EMAIL PROTECTED]/Documentation/user/lilypond.pdf,PDF} and as a
[EMAIL PROTECTED]/Documentation/user/lilypond/index.html,standard indexed
multi-page}.
[EMAIL PROTECTED] ifset
@end ifhtml
-- Forwarded message --
From: Francisco Vila [EMAIL PROTECTED]
Date: 2008/12/3
Subject: Re: one big page refers to itself
To: -Eluze [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
2008/12/2 -Eluze [EMAIL PROTECTED]:
the first sentence in NR
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-big-page.html is:
*This document is also available as a PDF and as one big page.*
which is a reference to itself …
shouldn't the *big-page* point to the pdf and index version
the *pdf* to the index and big-page version
and the *index* to the pdf and big-page version?!
Thank you. I think I could fix this implementing your solution, it is
easy as we have texinfo macros @ifhtml, @ifset bigpage and @ifclear
bigpage. Gimme some time.
--
Francisco Vila. Badajoz (Spain)
http://www.paconet.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: wrong link in AU 2.11.64
On 2008/11/29 11:49 +0100, james wrote: I don't know if it's true in other versions, but in Application Usage, 1.2.2 Requirements, the link to fontconfig points to http:// www.freetype.org, but it should probably point to http:// fontconfig.org/ Unless there is a fontconfig at freetype.org that I just didn't see. Thanks, fixed. Best, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Spanish Translation
You only need to - create a messages_es.properties file besides the messages.properties, and - create a LilyPondTool_es.props file containing the messages from the LilyPondTool.props file. - the LilyPondTool_es.props file shouldn't contain anything but localized messages - the localization files shouldn't contain non-ascii (not even latin1-extended) characters. Instead we must use the unicode character code in \u003b format. It can be solved by a simple searchreplace or there are tools for this. After doing this, the LilyPondTool_es.props file must be placed into the properties folder of jEdit along with other localization files. Actually jEdit can be localized this way: you just override some properties coming from other places - most plugins can be translated this way as they use this method for localization. For example if you look at Console plugin source, you can translate the messages from Console.props and put your .props file into the properties folder of jEdit. Unfortunately this method sucks but there is no better way. The message_es.properties files follows the normal way: it will be automatically loaded if JEdit/LilyPondTool is run on a machine with es locale set. Bert Francisco Vila wrote: Hello Bertalan, I'd like to translate jEdit + LilyPondTool into Spanish. You told me that there was a translatable resource file. Where is it? Would be possible to include the Spanish localization as standard and make it work automatically in Spanish environments? The same goes for jEdit, I don't know if you could help me on that. Thankyou ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problems building documentation
Le mardi 02 décembre 2008 à 04:59 -0800, Graham Percival a écrit : On Tue, Dec 02, 2008 at 06:17:57AM -0600, Jonathan Kulp wrote: OK it exited with error messages but I think it all built properly anyway: ce to nonexistent node `Keyboard instruments' (perhaps incorrect sectioning?). /home/jon/lilypond/Documentation/fr/user/out-www//specialist.texi:19: Menu reference to nonexistent node `Keyboard instruments' (perhaps incorrect sectioning?). The French translation is screwed up. I can't imagine how they missed the entire keyboards chapter, though... I can't reproduce that error with latest master merged with lilypond/translation, but current Git master should build succesfully even with makeinfo. Docs building fails for Jonathan but not for me because texi2html is tolerant with this kind of sectioning errors whereas makeinfo is not. As soon as texi2html 1.79 is out, I'll remove support for makeinfo --html. Cheers, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fwd: one big page refers to itself
On 2008/12/03 16:09 +0100, Francisco Vila wrote: Hello, I've fixed and tested this in html NR. Looks good? Please suggest a possibly better string for the not-single-big-page link. Tested and LGTM, except I'd suggest HTML indexed multiple pages instead of standard indexed page. Cheers, John PS : for future in-line patches, please turn line wrapping off in your email client. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
A naive question about permissions in buildscripts/
Hi, I notice Werner recently changed the permissions on a lot of files, including makelsr.py. Can somebody explain how I'm supposed to run these files without using chmod to change the permissions back temporarily? Cheers, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: A naive question about permissions in buildscripts/
Hi Neil, On Thu, Dec 04, 2008 at 01:23:59AM +, Neil Puttock wrote: I notice Werner recently changed the permissions on a lot of files, including makelsr.py. Can somebody explain how I'm supposed to run these files without using chmod to change the permissions back temporarily? You should be able to do $ python buildscripts/makelsr.py and include the options on the end. HTH, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: A naive question about permissions in buildscripts/
On Thu, Dec 04, 2008 at 01:23:59AM +, Neil Puttock wrote: I notice Werner recently changed the permissions on a lot of files, including makelsr.py. Can somebody explain how I'm supposed to run these files without using chmod to change the permissions back temporarily? Well, you could run python makelsr.py I'm not sure why he changed the permissions, though. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: A naive question about permissions in buildscripts/
I notice Werner recently changed the permissions on a lot of files, including makelsr.py. Can somebody explain how I'm supposed to run these files without using chmod to change the permissions back temporarily? You shouldn't use the versions in `buildscript' at all. Instead, use the versions in `buildscript/out' which (a) have all @...@ variables substituted correctly and (b) have the right permissions. Well, you could run python makelsr.py Is there ever need to do that? I'm not sure why he changed the permissions, though. I did this for orthogonality with the many python scripts in this directory which already had no executable bit -- additionally, it is a hint to not execute the scripts directly but use the versions in `out'. BTW, isn't it an error that `makelsr.py' starts with #!/usr/bin/env python instead of [EMAIL PROTECTED]@ ? The same is true for check_texi_refs.py check_translation.py coverage.py find-superfluous-includes.py fixcc.py git-update-changelog.py manuals_definitions.ly musicxml_generate_intervals.py musicxml_generate_keys.py musicxml_generate_timesignatures.py mutopia_index.py readlink.py tely-gettext.py translations-status.py And why does `output-distance.ly' use [EMAIL PROTECTED]@' inspite of being in `buildscript'? Shouldn't this be [EMAIL PROTECTED]@' also? Otherwise, there should be a comment... Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
