2013/1/14 Federico Bruni fedel...@gmail.com:
I've never worked at the translation of a manual which uses gettext.
For example the GIMP manual is translated using gettext.
http://l10n.gnome.org/module/gimp-help-2/
a POT per chapter, a PO per chapter/language
The workflow in GNOME is:
log in
As responsible for the Hungarian translation, what are the exact steps I
should perform in order to solve this?
2013/1/13 Francisco Vila paconet@gmail.com
2013/1/13 Federico Bruni fedel...@gmail.com:
Il 13/01/2013 11:45, Francisco Vila ha scritto:
Oh sorry! you mean PDF of the
2013/1/14 Harmath Dénes harmathde...@gmail.com
As responsible for the Hungarian translation, what are the exact steps I
should perform in order to solve this?
Hi Darmath
I don't think it's your duty, the problem is in the build system.
Honestly, I don't know why the links change depending on
Harmath Dénes harmathde...@gmail.com writes:
2013/1/13 Francisco Vila paconet@gmail.com
the dead links to web.xx.pdf occur only on certain languages:
fr, de, cs, hu
for 'es' the link is alive but points to untranslated web.pdf
As responsible for the Hungarian
[...] I can't help the impression that we have, for several
languages, people who feel responsible for maintaining the
translations but are unaware that many translations are severely
outdated and not really all that useful any more for working with
the current version of LilyPond: partly
2013/1/14 David Kastrup d...@gnu.org
The only translations that appear to be thoroughly maintained are the
Spanish and French translation, with the German translation following
close behind.
Well, the italian translation is far to be completed but it _is_ maintained.
It would a
2013/1/14 Werner LEMBERG w...@gnu.org
I wonder what's the best way to update outdated documentation.
Reading the whole documentation and checking the translation is
probably quite hard and needs a lot of time. Would it be better
instead to use a git repository viewer, walking over the
Federico Bruni fedel...@gmail.com writes:
2013/1/14 David Kastrup d...@gnu.org
The only translations that appear to be thoroughly maintained are
the
Spanish and French translation, with the German translation
following
close behind.
Well, the italian
So how can we improve the efficiency of our current translation work
force, and how can we make it easier for people to help in a way
that does not step on anybody's toes and actually leads to better
results?
Yeah. Let's assume that I would like to quickly improve various
places of the
2013/1/14 Werner LEMBERG w...@gnu.org
So how can we improve the efficiency of our current translation work
force, and how can we make it easier for people to help in a way
that does not step on anybody's toes and actually leads to better
results?
Yeah. Let's assume that I would like
Hello,
On 14 January 2013 12:52, Federico Bruni fedel...@gmail.com wrote:
2013/1/14 Werner LEMBERG w...@gnu.org
So how can we improve the efficiency of our current translation work
force, and how can we make it easier for people to help in a way
that does not step on anybody's toes and
2013/1/14 Werner LEMBERG w...@gnu.org:
I wonder what's the best way to update outdated documentation.
Reading the whole documentation and checking the translation is
probably quite hard and needs a lot of time. Would it be better
instead to use a git repository viewer, walking over the
Werner LEMBERG w...@gnu.org writes:
So how can we improve the efficiency of our current translation work
force, and how can we make it easier for people to help in a way
that does not step on anybody's toes and actually leads to better
results?
Yeah. Let's assume that I would like to
2013/1/14 David Kastrup d...@gnu.org:
[...] I can't help the impression that we
have, for several languages, people who feel responsible for maintaining
the translations but are unaware that many translations are severely
outdated and not really all that useful any more for working with the
2013/1/14 David Kastrup d...@gnu.org:
Probably the CG should be updated, improved and simplified.
I think that at the moment it would be a bit hard for a new translator
to get in.
And I think we could make of several new ones or, probably needing
similar measures, reactivate some old ones.
2013/1/14 David Kastrup d...@gnu.org:
We have a translation branch, but for typos, I think (correct me if I am
wrong) that of little relevance as we have back-and-forth merging.
Right.
Factual errors occuring only in one translation should be fixed there.
Factual errors inherited from the
Francisco Vila paconet@gmail.com writes:
2013/1/14 David Kastrup d...@gnu.org:
Probably the CG should be updated, improved and simplified.
I think that at the moment it would be a bit hard for a new translator
to get in.
And I think we could make of several new ones or, probably needing
I think this thread has moved too fast and we could have a problem of
time zones here. Sorry for answering on a one-by-one basis but it
worths it. The thread is asking many questions and I have some
answers. I don't want you to think I am not concerned with the issue.
2013/1/14 James
2013/1/14 David Kastrup d...@gnu.org:
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
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:
2013/1/13 Federico Bruni fedel...@gmail.com:
Il 13/01/2013 11:45, Francisco Vila ha scritto:
Oh sorry! you mean PDF of the translation of the web document.
http://www.lilypond.org/development.de.html links to web.de.pdf but
you are right, this is a dead link.
the dead links to web.xx.pdf
21 matches
Mail list logo
