Re: [lantern] Put documentation in to transifex (#1190)

[_pa...@getlantern.org]

Hey @tlevinson,

Making a separate "Lantern Documentation" project on Transifex, and making each page a separate resource therein, sounds like the best way to go. That's what e.g. https://www.transifex.com/projects/p/commotion-documentation/ is doing (see their [resources](https://www.transifex.com/projects/p/commotion-documentation/resources/)) vs. e.g. https://www.transifex.com/projects/p/commotion-user-interface/

Here are the docs on Transifex's Translation Memory:

http://support.transifex.com/customer/portal/articles/1156770-translation-memory

I think we should still be able to share translations from between our two different Transifex projects. It's also simple to set up a .tx/config file to pull from resources across different projects into the same repo:

http://support.transifex.com/customer/portal/articles/1000855-configuring-the-client

Copying Dragana and the lantern-i18n list in case anyone else has any input.

Thanks for all your help!

On Sun, Feb 9, 2014 at 2:09 PM, tlevinson <notifi...@github.com> wrote:

@cholmes, @skivvies

Chris fyi - I started adding some docs to transifix today. I uploaded a single file for the Downloading topic and gave it a category (Documentation).

_pants pointed out this doesn't really fit with the hierarchy on how the other resources are set up, which makes sense, as the other resources are high-level categories. He suggested putting the documentation in a separate project as an alternative.

Uploading all the documentation in one resource in the current project doesn't seem like the best approach to me. For one thing, it makes it harder to figure out which topics have been translated and which have not. Secondly, it will be easier to just export a translated file and add it to the docs.

I like the idea of a separate project but not 100% clear on what we might lose if the doc strings are kept separate from the other strings. Trying to figure out now if we can use the same Glossary for the separate projects.

Thoughts on this? If we do want to keep in one project, it seems like using the Category option is a good compromise. If it's really important to have all the documentation strings in one resource, I can live with it.

—
Reply to this email directly or view it on GitHub.