Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide translation format interop #60

Open
Hotell opened this issue May 3, 2019 · 6 comments
Open

Provide translation format interop #60

Hotell opened this issue May 3, 2019 · 6 comments
Labels
enhancement New feature or request

Comments

@Hotell
Copy link

Hotell commented May 3, 2019

Hey folks!

I got 2 important questions to consider this in our next project:

  • Does this somehow support exporting to .mo files and vice versa ?
  • If not is there any open source tooling that you're using for translators ?

Cheers

@w1106c
Copy link
Contributor

w1106c commented May 3, 2019

Thanks for reaching out to us Hotell!

  1. Currently, we do not support exporting to .mo files but we will look into it and evaluate this option.
  2. We do not directly support any open source tooling at this point either. However, the output and input formats are not super complex, so I would imagine it to not be too hard to make these work with open source tools.

@AndrewCraswell
Copy link

@w1106c, @jrwats I'm getting ready to localize an application that we would like to use FBT for and this question is super relevant. I'm interested in your experience working with vendors to do the actual translations. Were FBT's JSON files designed to be compatible with some of the more popular translation file formats for tools used by translators, or is it a brand new standard? Or do you just give the raw JSON to translators and have them edit the same files inline?

@jrwats
Copy link
Contributor

jrwats commented Sep 30, 2019

@AndrewCraswell, we actually have an internal tool to which vendors have access and through which they submit translations. They're shown the source string and description (as seen in the JSON output), and for any given parameter, they have the option to specify different strings depending on the variation of the parameter. These variations are determined on a per-locale basis.

We don't show them raw JSON

@jrwats
Copy link
Contributor

jrwats commented Sep 30, 2019

I'll take today to look at how difficult it'd be to produce a POT file from FBT collection and similarly, ingest a PO file(s) for translation.

@AndrewCraswell
Copy link

That would be incredible. I think if something along those lines could become a feature than this library would be a perfect replacement for many existing localization libraries.

@jrwats
Copy link
Contributor

jrwats commented Oct 10, 2019 via email

@jrwats jrwats added the enhancement New feature or request label Jul 17, 2020
@jrwats jrwats changed the title question on tooling for translators Provide translation format interop Jul 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants