[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1635 in lilypond: clean up misleading warnings in website buil
From: |
lilypond |
Subject: |
Re: Issue 1635 in lilypond: clean up misleading warnings in website build |
Date: |
Thu, 28 Apr 2011 23:43:27 +0000 |
Comment #9 on issue 1635 by percival.music.ca: clean up misleading warnings
in website build
http://code.google.com/p/lilypond/issues/detail?id=1635
I took a quick look at this. It looks like extract_texi_filenames.py
creates the xref files, which are used to allow us to do things like
@rlearning{blah}
As such, they definitely are required for the website to function, so
ignore the comment about translations above. (xrefs do aid the translation
infrastructure, but they're also used in the English-only builds)
However, it's probably still worth investigating the translations. Are
these warnings coming from the English extract_texi, or the translation
extract_texi, or only one or two translations, or what? (adding "echo
here1", "echo here2", etc to website.make may help here)
Another route of attack would be to look at exactly what arguments are
given, figure out if the file in question actually exists or not, and then:
- if the file exists, why doesn't extract_filename ignore it?
- if the file doesn't exist, then why does the makefile try to extract_texi
on it?
Either or both could be the cause of these warnings.
- Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/25
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/26
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/26
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/27
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/27
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/27
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/27
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/28
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/28
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build,
lilypond <=
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/28
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
- Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29