Get started localization with Lokalise.co (FOLIO-1143)

[FOLIO-1144] Discuss about localization workflow with Jakub Created: 20/Mar/18  Updated: 12/Nov/18  Resolved: 23/Mar/18

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None
Parent: Get started localization with Lokalise.co

Type: Sub-task Priority: P3
Reporter: István Bender Assignee: István Bender
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:

 Description   

We have to discuss about GitHub integration, security settings, branching, etc.



 Comments   
Comment by István Bender [ 23/Mar/18 ]

Jakub:

"The bottom line, though, is that whatever tool we use to manage translations, it should not interfere with the dev process and the way we store/load translation files. Right now the translations are stored in app's repo in JSON files, with react-intl syntax and a PR is needed for any change that should be merged to the mainline. This is consistent for "core" UI apps but external teams may be doing things differently. Both tools seem versatile enough to deal with it though. One feature I felt was missing – and I mentioned this to Istvan – was some indication, e.g a simple highlight, that interpolation placeholders (like in "

{count}

record found") are special should be treated with care by translators (e.g NOT translated). This may be too much to ask for though.

Let's give Lokalise a try and see what the feedback from translators is."

Generated at Thu Feb 08 23:11:09 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.