Re: GDP: translations and code comments

[Francisco Vila]

2008/4/19, Graham Percival <address@hidden>:
> On Thu, 17 Apr 2008 09:54:39 +0200
>
> "Francisco Vila" <address@hidden> wrote:
>  > Text Markups: must translate and need recompilation.
>
>
> Surely not if they're musical terms like
>   \markup{ \italics dolce }
>  ?  (VV: ok, you win)

Trivially not. You know I'm thinking in different cases.

>  > Variable names: already translated in @examples, helps clarifying. It
>  > would be nice to have them translated in verbatim- and non-verbatim-
>  > snippets. Again, in verbatim mode the translated version could show
>  > and the original could be kept so it doesn't need recompilation.
>
>
> ... really?  A lilypond user needs to know *some* English anyway.
>  \relative, \transpose, \partcombine... if somebody has
>  trouble with
>   musicA = {...}
>   musicB = {...}
>  then how on earth will they understand
>   \once \override Voice.Stem #'padding = #3
>  ?
>
>  ... well, it's your time.  If you think it's worthwhile, go ahead.

I said 'helps clarifying' and they do. Software is software;
programming languages are programming languages (keywords are
keywords); but for manuals, tutorials, documentation in general, there
are several human languages other than English. My aim is to ease all
that is possible the utilisation to  non-English users, is that
simple.

When Han-Wen and Jan first made this wonderful program, they surely
decided no to use only Dutch or Portuguese keywords, they used English
keywords, that's fine, the world is a big place, but now is my turn
and everything that could possibly be in Spanish it will be if it
depends on me. The Spanish world is also a big place.

It is only my opinion, I know you support translation and I thank you for that.

BTW I have used (long ago) Spanish versions of MS Excel with
translated function names and these spreadsheet documents were not
compatible with anyone else. This is NOT what I want.

-- 
Francisco Vila. Badajoz (Spain)
http://www.paconet.org