This is a read only archive of pad.okfn.org. See the shutdown announcement for details.

writethedocs-l10n alternative notes - https://www.evernote.com/shard/s143/sh/4595280e-0b24-4618-b81d-3642ddf65ebf/5ef4ce9ec3b8244fc9e65cf8cfce1931

plone uses transifex and so does ckan
upload everything to transifex
the admin interface is a bit iffy but great for delegation
drupal has an open source tool for translating, doesn't have translation memory yet.
transifex isn't exactly lock-in because you pull out your translations
url scheme for lang and version

how to show people that they're on an outdated version of the documentation
drupal hasn't figured it out yet, but you can swap out text based on your version
sumo has versioning and languages
mdn doesn't have it yet
hard to do versioning on wiki
plone is in the process of scripting screenshots
Kristof is making the tool to do this using selenium

mozilla uses their awesome community!
firefox will have things that will highlight the bit you want to click when you're on SUMO.
writing robots reqires humans to touch XSLT

what do you with partial translations?
MDN  has a banner that will show up and say it's in progress with a call for action message.
Wikis don't have the ability to flag things on and off
The English bits get updated more faster than translations. If it's older than 5 years, hide translations because it's not worth it.
This is a hard problem to solve :)
You can measure the drifts somewhat, but the degree of change isn't easy.
Compare translations based on technical words and the place in the sentence?
(ali) Doing this in the past didn't help much despite using hardcore algorithms
You could set a flag that would alert people to look at the translations based on the English version changes
You can change 30% of the article but it didn't change from the localization standpoint.
Moz has a dashboard that shows l10n status which compares the original page
The dashboard helps contributors know when and which article to edit.

What  happens when languages other than English moves forward?
it's very tricky. Because you don't hvae a stable master. Needs to look into that community
Usually it's because that area of English documentation has been updated and we would need to fix that.
It could happen with FxOS when it's released into a specific market you may have things like this happening.
Also with stuff with local legal requirements, like accessibility law in Brazil

Wiki has no translation memory, but verbatim has some basic memory
zaneta is used by red hat. Launchpad also has translation interface, but it's bzr and with git and github, less people use it.
There's also transvision for the mozilla community
also, pootle.
There's a few vendors in this space now
microsoft has a thing for what MS cals a certain thing. Don't know yet if open source communities do that yet.
there would be a lot of value in making an open source translation memory
there were originally designed for macines, which was a big epic fail, it's been stagnating after that.

translations are the biggest feature for the thing that kristof will demo
how to manage and get people to collaborate is hard.
when you localize your tests start failing because your labels are changing.
You also need to translate selenium which isn't easy.
you also need to test that magic like plural words aren't broken in other locales (gettext)

xcliff is an xml language for translations
if you have docbook, you can use xcliff to turn it into something that you can use with translation tools
In the DITA world, there's several paid options for translations.

How to organize sources that can be efficiently translated
Always start with the langauge at the highest level, like url / en / things
Copy it over, harddisk space is cheap. Mistakes have been made and it's always messy to clean up.
It depends on your tool, some tools have immutables which are not translated by default.
Copy everything or use symblinks. Even images were not immutables, because it needs to be translated and the alt text needs to be translated.
Immutable will, at some point, be translated or need to be translated.

DITA has one single structure, drupal is similar. Huge pain in the back side ;)
It has a map, which can be referenced from elsewhere.
It's called transclusion.
It could also come into the WYSIWYG editors

As soon as you translate chunks you save a lot of money and time.
Chunking is harder with docbook where everything is one big xml monster.
Try to break it down as small as possible but sometimes you need context.
phrases are great to re-use.
German likes to put everything in one giant sentence, English likes to break it up
In theory translation memory would help with that. DITA translates on topic.
You separate out what requires needs context and what doesn't. code sample would be a different chunk.
More flexibility is great, because it's hard to definethis. Setting the boundary is the key.
https://pontoon-dev.mozillalabs.com/ lets you translate in place.