Hi Klaus,

In addition with Hannes say, perhaps you can start using the online editor (
https://edit.php.net).
This tools make a lot of things in the background who will help you on
common tasks with translation.

Best,
Yannick


2012/3/22 Hannes Magnusson <hannes.magnus...@gmail.com>

> On Wed, Mar 21, 2012 at 21:30, Klaus Silveira <klaussilve...@php.net>
> wrote:
> > Dear maintainers,
> >
> > I have a tricky question that you guys might be able to help by sharing
> your
> > experiences. The pt_BR build of the PHP documentation is very obsolete.
> > There are a lot of files that don't exist anymore in the EN build and
> lot's
> > of files from the current EN missing from the pt_BR build. Not only the
> > references are obsolete, the actual files are missing or should be
> removed.
> > Is there a quick way of syncing the two again, so we can start working
> on a
> > more stable and updated pt_BR build?
>
> The configuration scripts will automatically fallback to English files
> when files are missing in the translations - as long as the "container
> files" aren't overwritten (i.e. the files that contain the entity
> references).
>
> I would start with either making sure the "container files" are
> up2pdate, or removing them (files like book.xml which contain entity
> includes of classes and functions).
> That will ensure the fallback will kick in, and the English
> translation will be included when the translation is missing some
> files.
>
> If you have a lot of files in the translation that no longer exists in
> the english version, then those files have most probably be refactored
> into smaller chunks. They could also simply have been renamed (which
> we really really try to avoid exactly to prevent this sort of issues),
> but I would recommend you track down when the file was removed and why
> - just so you won't have to translate the entire thing again for no
> reason.
>
>
> I'm not a translator, so I can't say what other translations do..
> hopefully someone can explain what they do in these cases :]
>
> -Hannes
>

Reply via email to