| Re: [translations] Re: How to extract PDF of translated documentation? |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: David Kastrup <dak@xxxxxxx>
- Subject: Re: [translations] Re: How to extract PDF of translated documentation?
- From: Federico Bruni <fedelogy@xxxxxxxxx>
- Date: Mon, 14 Jan 2013 23:58:05 +0100
- Cc: Francisco Vila <paconet.org@xxxxxxxxx>, Harmath Dénes <harmathdenes@xxxxxxxxx>, lilypond-devel@xxxxxxx, LilyPond Translation <translations@xxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=VXUKN1cXHppYF3bW5cyVrcUEO9gb30rsUj4czMmKAXw=; b=prqWGdLv0uisgxNZlU1WzRRmqPpadG0xaC7EpaE/68XoihGjl6reqxhqziWwncRoL0 yv0Be321H86eq1lGlSqRCcvkJsaPMkNfmcsu7AQWsychbW0HzElQW40NBdvl2RxXRhH6 5rR9TmZOj8fW+GhdWGfOUP8wBcO/0YVt7hIOlKPf+RwH8XtvcG5KREDtIeTYnz6Exr6X vaXszLpQN+KzUibriFxnL9078VPLhJpZXEgNwxc157EthkEEk+XGfrfdm61aItPCbJz1 YXdMa/w0ZQaef6jvaf1dSubmAQeQErwcqYn7Vh+VoSQ7S78PYT+Are5YcsproYKnsIgo +fyw==
Il 14/01/2013 20:32, David Kastrup ha scritto:
Redundancy of contributors, or redundancy in CG to make things much
>easier to find?
Redundancy of contributions. We currently have "one person does the
translation once and nobody including himself looks at it ever after".
I've had a look here:
http://lilypond.org/translated.html
and it seems that this is true for any language except french and italian.
As you aptly observed, that's the best you yourself can barely manage
for Spanish. But I can't believe you to be the only LilyPond user
natively speaking Spanish. The main qualification we should be
requiring from translators and translation revisors is good command of
language. Not ability to juggle with git and other technical stuff.
My proofreader, Luca, is a huge help for the quality of italian words
and also the choice of musical terms (he studied music, while I'm just
self-taught and very ignorant in notation theory). He's scared away by
the technical stuff (which I'm happy to handle) and I remember that he
offered to help me provided that he didn't have to learn git, texinfo
and the build system.
So technical stuff can be handled by just one person per language.
Editing the italian words of a text file, ignoring any strange texinfo
command, and producing a diff file, is not an hard task... especially
for a LilyPond user :-)
So how can we move in a direction where translation work is less
technically challenging? I believe that with regard to the program
string translation (gettext, po, pot files or whatever), there is some
sort of process that detaches the language teams from the technical
details.
Maybe we can move more in that direction for the manual texts as well?
I don't have good suggestions here at the moment, but I should think
that there is potential for getting more people involved for making
their own language look better-suited for reading about and working with
LilyPond.
I've never worked at the translation of a manual which uses gettext.
The Debian Handbook can be a source of inspiration:
http://debian-handbook.info/contribute/
http://anonscm.debian.org/gitweb/?p=debian-handbook/debian-handbook.git;a=blob;f=README.translators;hb=master
https://fedorahosted.org/publican/
http://debian.weblate.org/projects/debian-handbook/
Did you know Weblate (it's GPL)?
http://weblate.org/en/
--
Federico