Re: [translations] Re: Problem with documentation download

2017-02-02 Thread Federico Bruni
Il giorno gio 2 feb 2017 alle 12:52, David Kastrup  ha 
scritto:
At the current point of time, building the Czech PDF file is not just 
a waste of time but also not helpful to the Czech users of LilyPond. 
If we can sensibly link to the English documentation, we should 
likely do that. Maybe we should offer an additional link to the 
English versions for _all_ languages knowing to have an outdated 
translation, including German and Dutch.


Ok, then I'll make sure that it will point to the English PDF file.

Some months ago I suggested using a warning for out-of-date translated 
pages:

https://lists.gnu.org/archive/html/lilypond-user/2016-11/msg00736.html

I've now added an issue on the tracker:
https://sourceforge.net/p/testlilyissues/issues/5048/

I'm going to label as "translations" the issues related with 
translation. Because searching in Sourceforge is a pain.



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


Re: [translations] Re: Problem with documentation download

2017-02-02 Thread Francisco Vila
2017-02-02 12:46 GMT+01:00 Federico Bruni :
> What's the reason for blocking the build of PDF files?

I don't remember but we should test it first and throw a look on it.

> If there's a good reason not to build the czech PDF file, then we should
> change it to link to the english PDF. File not found is not nice.

Of course I agree on this.

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

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


Re: [translations] Re: Problem with documentation download

2017-02-02 Thread David Kastrup
Federico Bruni  writes:

> Il giorno gio 2 feb 2017 alle 12:23, Francisco Vila
>  ha scritto:
>> 2017-02-01 17:08 GMT+01:00 Federico Bruni :
>>>  @TRANSLATORS: ok if I comment that line and push to translation
>>> branch?
>>
>> I don't oppose but those PDFs were not built for a reason.
>>
>>
>
> My change proposal was only for the czech documentation, which does
> not have an active maintainer AFAIK (not japanese or chinese).
>
> What's the reason for blocking the build of PDF files?
> If there's a good reason not to build the czech PDF file, then we
> should change it to link to the english PDF. File not found is not
> nice.

At the current point of time, building the Czech PDF file is not just a
waste of time but also not helpful to the Czech users of LilyPond.

If we can sensibly link to the English documentation, we should likely
do that.

Maybe we should offer an additional link to the English versions for
_all_ languages knowing to have an outdated translation, including
German and Dutch.

-- 
David Kastrup

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


Re: [translations] Re: Problem with documentation download

2017-02-02 Thread Federico Bruni


Il giorno gio 2 feb 2017 alle 12:23, Francisco Vila 
 ha scritto:

2017-02-01 17:08 GMT+01:00 Federico Bruni :
 @TRANSLATORS: ok if I comment that line and push to translation 
branch?


I don't oppose but those PDFs were not built for a reason.




My change proposal was only for the czech documentation, which does not 
have an active maintainer AFAIK (not japanese or chinese).


What's the reason for blocking the build of PDF files?
If there's a good reason not to build the czech PDF file, then we 
should change it to link to the english PDF. File not found is not nice.





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


Re: [translations] Re: Problem with documentation download

2017-02-02 Thread Francisco Vila
2017-02-01 17:08 GMT+01:00 Federico Bruni :
> @TRANSLATORS: ok if I comment that line and push to translation branch?

I don't oppose but those PDFs were not built for a reason.

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

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