On Thu, Jul 4, 2013 at 2:26 AM, Graydon Hoare <gray...@mozilla.com> wrote:
> On 13-07-03 05:06 PM, Tim Chevalier wrote: > > > I don't know of any such proposal already, so I encourage you to take > > the lead. Of course, even with the translations in the tree, there's > > the risk that they could become out of sync with the English version, > > but that's preferable to not having translations at all. (Perhaps > > other people who have been in projects with internationalized > > documentation can comment on the best approach(es) to this issue?) > > I was hoping we'd set up a pootle server to translate .po files, and/or > use the existing pootle instance mozilla runs: > https://localize.mozilla.org/ > > .po files aren't perfect, but they seem to be dominant in this space. > There are a lot of tools to work with them, show the drift from a > translation and its source, and reconstruct software and documentation > artifacts from the result. I think po4a might be applicable to the .md > files that hold our docs: > http://po4a.alioth.debian.org/ > > Someone who is familiar with these tools and workflows would be very > welcome here. We've had a few people ask and just haven't got around to > handling it yet. > > -Graydon > _______________________________________________ > Rust-dev mailing list > Rust-dev@mozilla.org > https://mail.mozilla.org/listinfo/rust-dev > I thought that .po files were mostly used to translate bits and pieces, such as strings used in GUIs, and not full-blown text files such as tutorials ? As to version drift, if both versions are in-tree it seems easy enough to check were made on the English version after the last commit of the Spanish version; you would just have to find the latest ancestor of both changesets and get all changes to the English version that are not in the Spanish branch. -- Matthieu
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
