Re: Discussed here: (issue 321830043 by address@hidden)

[Federico Bruni]

It won't be in english only. It's up to translators. With this patch they can:

a) not translate the file, so the content of that section will be in english 
_within a translated page_. No maintenance needed.

b) translate the file and maintain it across updates

I think I forgot to add a better comment at beginning of gsoc.itexi.
I will do it in the coming days.

Sorry for the bad email subject. I didn't realize until today how Rietveld 
creates it.

Il 31 marzo 2017 09:31:20 CEST, Urs Liska <address@hidden> ha scritto:
>I don't really know what that technically means, but I'm OK with having
>the GSoC page in English only.
>
>This page is being heavily edited for a certain period each year, and
>the "target audience" has to be able to read it in English anyway.
>
>Urs
>
>
>Am 31.03.2017 um 09:06 schrieb address@hidden:
>> Reviewers: ,
>>
>> Message:
>> Please review
>>
>> Description:
>> Discussed here:
>>
>https://lists.gnu.org/archive/html/lilypond-devel/2017-03/msg00277.html
>>
>> web: move Google Summer of Code information in included/
>>
>> So translators can choose not to translate this node of
>community.itexi.
>> GSoC page gets quite frequent updates and keeping the translations
>> up-to-date may be cumbersome and not worth the effort (as GSoC
>> applicants are required to speak english).
>>
>> Please review this at https://codereview.appspot.com/321830043/
>>
>> Affected files (+401, -385 lines):
>>   A Documentation/included/gsoc.itexi
>>   M Documentation/web/community.itexi
>>
>>
>>
>> _______________________________________________
>> lilypond-devel mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/lilypond-devel
>
>-- 
>address@hidden
>https://openlilylib.org
>http://lilypondblog.org
>
>
>_______________________________________________
>lilypond-devel mailing list
>address@hidden
>https://lists.gnu.org/mailman/listinfo/lilypond-devel