Re: [translations] Re: not translating a node in a file |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: Francisco Vila <paconet.org@xxxxxxxxx>
- Subject: Re: [translations] Re: not translating a node in a file
- From: Federico Bruni <fede@xxxxxxxxxxxxx>
- Date: Thu, 30 Mar 2017 16:33:31 +0200
- Cc: Translations list at lilynet <translations@xxxxxxxxxxx>, "lilypond-devel@xxxxxxx" <lilypond-devel@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inventati.org; s=stigmate; t=1490884448; bh=Q2E934gwtTl8nfNOtSptzKEHI4VpxbUSN7np00U3E2E=; h=Date:From:Subject:To:Cc:In-Reply-To:References; b=sWR1QKc9oXqgE1+z+UoOurglFOvoVktnfirSzuzT4vsVdU7PgvOsNXreqYh0zpsDl mBBPX7rJF0E2aNSQquuE1qJ8xV1Iy0Cwo/GQDrd0lodyYQJC1llsHJfUN5vfqXlXZV AMKjEt7NeZASXGBQscK/ARk4npTX7pnBRjKK/EV4=
Il giorno gio 30 mar 2017 alle 14:08, Francisco Vila
<paconet.org@xxxxxxxxx> ha scritto:
2017-03-30 13:07 GMT+02:00 Federico Bruni <fede@xxxxxxxxxxxxx>:
Continuous changes to Google Summer of Code node made me think
about
removing the translation, because maintaining the translation is
too
cumbersome and it's not worth (as any GSoC candidate should speak
english).
The problem is that I do not want to throw away all the community
italian
file, of course.
When I run "make website" after applying above change I get a 404
error
when I try to open the italian GSoC page.
So the italian node is not created.
It's a bug or I'm missing something? (see patch attached if you
want to
try it out)
An alternative might be moving the GSoC page in an includable file
(in
Documentation/included/), so we can easily include the english
text in a
localized website.
...
Today I had the chance to run 'make doc' and in this case the GSoC
page is
generated, BUT it's all (including menu and footer) in english.
What do you think about moving the GSoC node to
Documentation/included?
I may give it a try if there's no objection.
I think the @untranslated option is better because it does not mean a
change for original English authors, but otherwise I put no objection.
I would agree if:
1. menus, footer, etc. were not in english
2. it wouldn't break 'make website' (see below)
I could be wrong but make website is intended to be triggered after
any successful make doc, that's why it didn't work for you at first.
I've run 'make website' again after a successful 'make doc' (and after
"touching" all the files in Documentation/it/web). Again no
google-summer-of-code.it.html file generated:
$ find out-website/website/ -name google-summer-of-code*
out-website/website/google-summer-of-code.en.html
out-website/website/google-summer-of-code.de.html
out-website/website/google-summer-of-code.fr.html
out-website/website/google-summer-of-code.html
out-website/website/google-summer-of-code.es.html
out-website/website/google-summer-of-code.nl.html
out-website/website/google-summer-of-code.ja.html
I'll propose a patch to move the english node.