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

EPIC: about translation #11

Open
11 of 14 tasks
maxkoryukov opened this issue Aug 14, 2016 · 17 comments
Open
11 of 14 tasks

EPIC: about translation #11

maxkoryukov opened this issue Aug 14, 2016 · 17 comments

Comments

@maxkoryukov
Copy link
Member

maxkoryukov commented Aug 14, 2016

Provide toolset for the i18n and l10n features.

Main questions

Services

Discover and test services

  • 👎 https://www.oneskyapp.com/

    • no few formats supported (no json for react-intl)
  • https://www.transifex.com/ CURRENT CHOICE

  • https://poeditor.com/pricing/

    • good for tiny and medium projects
    • main target - PO files, not the json.
    • no ICU support
  • 👎 https://lingohub.com/

    • no ICU support
    • no tricky UI (but better than phraseapp)
    • no help with pluralization
  • 👎 https://phraseapp.com/

    After PO-editor, crowdin and transifex - phraseapp WebUI is not convenient(

    • no ICU
    • no UI
    • no help with pluralization
  • 👍 https://crowdin.com/

    ICU 👍

    We are already on the final stage of polishing the ICU support. We will support ICU-format for messages.
    It should be available on production within a week or earlier.
    You may also find useful this article. Here XLIFF file format is recommended for usage.

  • 👎 https://www.locize.io

    • NO collaboration tools
    • YES ICU support
    • NO pluralization helpers
    • UI - minimalism-guided, looks good

Useful tools and links:

Discussion about tools:

Other solutions:

Other related issues

Discussions in other projects

@maxkoryukov maxkoryukov added this to the Necessary articles milestone Aug 14, 2016
@maxkoryukov
Copy link
Member Author

maxkoryukov commented Oct 19, 2016

Transifex:

Common name schema: translations/<project_slug.resource_slug>/<lang>.<type>

@maxkoryukov
Copy link
Member Author

maxkoryukov commented Oct 20, 2016

RIght now there is no service, that works with ICU messages and/or ICU-bundles (files with ICU messages).

Transifex doesn't allow to work with ICU, but it allows to translate JSON files.
On other hand, Transifex handles pluralization just for XLIFF and PO-gettext formats. Pluralization is not necessary right now, but in the future it could be very useful

So, current decision:

  1. use Transifex with XLIFF.
  2. on Build (gulp) create a JSON object with ICU messages from XLIFF file (there are several npm packages)

And remaining problems:

1 determine, how to format XLIFF with plural and select features (ICU stuff)
2 search for appropriate XLIFF -> JSON converter and appropriate HBS and Ember helpers (and nodejs lib) to get acceess to converted JSON

NPM packages

NON ICU

@maxkoryukov
Copy link
Member Author

@maxkoryukov
Copy link
Member Author

@maxkoryukov
Copy link
Member Author

maxkoryukov commented Oct 25, 2016

ISO8601 and custom formatting for dates in ICU

Bunch of issues, created in other repos, to find a easy way of custom formatting for date-variables:

Every issue about problem with custom format string for dates (details on stackoverflow)

@maxkoryukov
Copy link
Member Author

There is one alive and beauty repository: https://github.com/messageformat/messageformat.js

I think, it is not a bad solution for the server-side translations (outside of HBS).

But! There is no neither HBS-helper nor Ember-package..

@maxkoryukov maxkoryukov changed the title Article: about translation EPIC: about translation Dec 27, 2016
@maxkoryukov maxkoryukov removed the pr:LOW label Mar 8, 2017
@maxkoryukov
Copy link
Member Author

Watch this too: TryGhost/Ghost#5345

@maxkoryukov
Copy link
Member Author

@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, ...)

@maxkoryukov
Copy link
Member Author

@jamuhl , thank you for a good advice;)

I tried to work with locize, but I ran into difficulties (mentioned in the first message). But it seems like new Locize dropped all cons))

Just give me some time for tests, our dev-resources are very limited...

@jamuhl
Copy link

jamuhl commented Nov 1, 2017

@maxkoryukov awesome...no need to rush...would be awesome if you could provide us with feedback if something could be changes or added to make it perfect. Luckily were still at a point were we add features and could optimize the system. So if there is something wrong, or could be better or needed (additional format for import/export) let us know...

@maxkoryukov
Copy link
Member Author

top 30 languages:

  • Afrikaans
  • Arabic
  • Catalan
  • Chinese Simplified
  • Chinese Traditional
  • Czech
  • Danish
  • Dutch
  • English
  • Finnish
  • French
  • German
  • Greek
  • Hebrew
  • Hungarian
  • Italian
  • Japanese
  • Korean
  • Norwegian
  • Polish
  • Portuguese
  • Portuguese, Brazilian
  • Romanian
  • Russian
  • Serbian (Cyrillic)
  • Spanish
  • Swedish
  • Turkish
  • Ukrainian
  • Vietnamese

@jamuhl
Copy link

jamuhl commented Jan 12, 2018

@maxkoryukov hope you already got time to checkout locize new ICU support - feedback would be awesome and like said we would love to extend imports if there is some special message catalog we do not yet support...

@maxkoryukov
Copy link
Member Author

@jamuhl, we are testing Locize on this week

First results: our translators tried to use Locize, but we didn't even start to test ICU, because I18N-team found that UI is not convenient for work.

Moreover, they told me, that Locize doesn't support the translation for DOCX-files.

@jamuhl
Copy link

jamuhl commented Apr 11, 2018

@maxkoryukov yes...we only offer translation of "technical" code projects. The UI does not offer options to translate docs, pdf, ... our focus is really to be strong on continuous localization of software projects not on translating manuals, ...

Would be great to hear what they did not like...guessing they come from a SDL trados world and not from software translation

@jamuhl
Copy link

jamuhl commented Apr 11, 2018

beside to simplify react-intl integration there is now also https://github.com/maciejw/react-intl-namespaces

  • enables multiple files
  • enables incontext editing

@maxkoryukov
Copy link
Member Author

maxkoryukov commented Apr 11, 2018

@jamuhl maybe soon I'll publish the summary of their reviews;)

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

No branches or pull requests

2 participants