Re: [translations] Re: not translating a node in a file

[ Thread Index | Date Index | More lilynet.net/translations Archives ]


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 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.

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



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/