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

[FOLIO-1146] Setup Lokalise projects Created: 20/Mar/18  Updated: 12/Nov/18  Resolved: 25/Jun/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: 15 minutes
Original estimate: Not Specified

Sprint:

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

How do we plan the lokalise projects? All UI modules will have different project, or all modules in one project?

Comment by Peter Murray [ 23/Apr/18 ]

Hmmm. If Lokalise supports it, I think all modules in one project would be easiest for the translators to understand.

Comment by István Bender [ 23/Apr/18 ]

Both is supported. All in one or separate projects per UI module. We discussed about this with Jakub an Cate. No decision yet. There are pros and cons in both cases.

Comment by Cate Boerema (Inactive) [ 23/Apr/18 ]

Sounds like we are all leaning towards all modules in one project, as the best option from the translator's perspective, though. Do we need to collect more information on this or can we proceed with this as the decision. Peter Murray, what do you think?

Comment by Peter Murray [ 23/Apr/18 ]

I'm going to try setting up a few of the ui- GitHub repos in the single project and we'll see how they look.

Comment by Peter Murray [ 23/Apr/18 ]

For FOLIO-1147 Closed I set up the GitHub integration for three ui-* modules:

  • ui-calendar: set up without the Include full path in the filenames option
  • ui-users: set up without the Include full path in the filenames option
  • ui-inventory: set up with the Include full path in the filenames option

All of the keys for all of the GitHub modules were put into one space without a way to distinguish where they translation keys came from. The on-screen tooltip for Include full path in the filenames option says:

> Turn on to include relative directory name in the filename. Useful if your localization directory has a complex subfolder structure, in all other cases it is recommended to use exporter options. In case you have existing files in the project, make sure the files already contain path in the filename to avoid creation of duplicates.

Unfortunately, on the Lokalise Projects screen that didn't help distinguish which ui-* project the key came from. And I can see that being a problem.

Michael Winkler: Given the Open Source license that we have with Lokalise, is it possible to set up more than one project in the Open Library Foundation team? On the top-level Lokalise page, I'm seeing the message "You are not allowed to create projects or orders in this team."

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