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

Translation services accepting ICU? #82

Closed
vonovak opened this issue Sep 13, 2017 · 6 comments
Closed

Translation services accepting ICU? #82

vonovak opened this issue Sep 13, 2017 · 6 comments
Labels

Comments

@vonovak
Copy link
Collaborator

vonovak commented Sep 13, 2017

hi! I understand that I can get the catalog from lingui and send that to translation, as outlined here, however, not many translation services work with ICU message format. Can somebody point me to tools that work on Mac and are able to convert ICU to XLIFF, which is the translation industry standard?

Can somebody point me to translation services that accept (ie. are able to translate) ICU?

the ICU website mentions genrb but I'm not sure it's available on mac.

also see formatjs/intl-messageformat#106

thanks!

@tricoder42
Copy link
Contributor

I'll take a look at possible options. As far as I understand it, ICU MessageFormat is format of messages, while XLIFF is format of a message catalog.

Here's similar issue formatjs/babel-plugin-react-intl#7

@tricoder42 tricoder42 changed the title [question] how do you distribute message catalogs to translators? Exporting message catalog to XLIFF Sep 29, 2017
@vonovak vonovak changed the title Exporting message catalog to XLIFF Translation services accepting ICU Oct 10, 2017
@vonovak vonovak changed the title Translation services accepting ICU Translation services accepting ICU? Oct 10, 2017
@jamuhl
Copy link

jamuhl commented Oct 29, 2017

We now fully support icu format at https://locize.com (and plan to extend based on your feedback / demand):

  • highlighting
  • validation
  • machine translations
  • plural conversion between source and target language
  • prettify of your icu strings

screen shot 2017-10-29 at 14 12 00

Your feedback would be very welcome - also if someone could provide us with a file extracted we could look into supporting that for importing (beside xliff, json, ...)

@tricoder42
Copy link
Contributor

@vonovak Hi, sorry I miss the update of your question.

There're many mature services online which support ICU message format:

Feel free to reopen if you had more question!

@Hotell
Copy link

Hotell commented Jun 26, 2019

I would reopen this issue.

Current version of lingui doesn't export valid getext nor json, when Plural -> ICU is used within codebase.

I've pinged PhraseApp folks. They're telling me that they support ICU but on the other hand, they have basically no idea, what format is supported regarding ICU (JSON/po). Their docs doesn't mention anything related to ICU -> .po nor .json support this format. (https://phraseapp.com/docs/guides/formats/)

I would appreciate ( and I guess anyone new coming to this library ) to get some info regarding Translation services compatibility.

Related:

Thanks

@jamuhl
Copy link

jamuhl commented Jun 26, 2019

@Hotell you can give https://locize.com a try...you can import / export both .json or .po -> also it should take the extracted file from jslingui as source - if there should be changes meanwhile just send us a file over to support@locize.com and we will check that so import gets updated to latest.

@tricoder42
Copy link
Contributor

Current version of lingui doesn't export valid getext nor json, when Plural -> ICU is used within codebase.

Why the exported PO file isn't valid? Is it because ID is missing as you described in other issue or the file itself isnt' syntactically valid?


Transifex and Crowdin, two biggest localization management platforms which I know, seem to support both PO files and ICU MessageFormat.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants