If you switch to gettext PO, translators may work offline using specialized PO
editors -
like GTranslator, Lokalize, which offer translation memory and glossary feature,
which will help them save their time and increase translation quality.
To manage translations, Fedora uses Transifex, a tool which I
co-develop. Transifex presents translators with statistics, allows
them to get the files and submit them back directly to the source
versioning system via an easy-to-use web interface. The actual
translation can be done either using a
a) As Philip mentions, the revision handling is a very basic thing
that is taken for granted right now, but the time will come when we
can't rely on CVS's automatic handling of $Revision$ strings anymore.
This system could be emulated on different VCS using pre-commit hooks,
which most if not al
C. Translating markup and related worries:
Whether or not an XML markup change affects translations shouldn't be
on our minds, but today it must be. Currently all changes, markup or
otherwise, affect the status of a translation. Ideas were explored to
help solve this symptom but nothing great ca
Hello friends of SPL,
A script now exists (phpdoc/scripts/check-missing-spldocs.php) that
tells us about missing and partially completed SPL documentation. It
makes a couple of assumptions (see script for details) but feel free
to use it.
If you're either working on something listed here
Folks:
It would be neat if people on the doc team could subscribe to a page so
the person could be notified when new comments are made. This will be
helpful for someone who has edited the page and/or culled the existing
user notes so the person can edit/curate comments as they come in.
--Dan
-- Forwarded message --
From: Philip Olson
> 3. Totally rethink the system
> My gut says move towards a gettext based system with po/pot files
+1 for that.
It'll take a long time to "re-translate" the whole thing, but I think it's
for the better. :)
>Regards,
>Philip
Cheers,
Hi Laurent,
> As I prefer to avoid cross posting, I just want to say that I found a
> possible render problem (found on PEAR Manual build).
>
> See my post [1], it's related to DocBook5 source code just committed
> [2]
>
> In summary two different render:
>
> -> ->
> ==> text intro follow
