organicmaps/twine
Archived
13
Fork 0
Code Issues 1 Pull requests 2 Projects Releases Wiki Activity Actions

WIP: Adjust Twine format to OrganicsMaps usages #13

Draft
dwaynebailey wants to merge 5 commits from rdb-twine-extract into organicmaps
pull from: rdb-twine-extract
merge into: organicmaps:organicmaps
Conversation 2 Commits 5 Files changed 1 +28 -14
dwaynebailey commented 2024-09-18 20:28:24 +00:00 (Migrated from github.com)
Copy link

This adjust the Twine output format to align with the existing Twine strings.txt in OM

Changes:

  • Space indent instead of tab
  • Dev language after metadata
  • metadata order aligns with existing
  • en-GB follows en

Problems:

  • Plurals are not extracted at all
  • The fancy \n\n in Android is very broken
This adjust the Twine output format to align with the existing Twine strings.txt in OM Changes: * Space indent instead of tab * Dev language after metadata * metadata order aligns with existing * en-GB follows en Problems: * Plurals are not extracted at all * The fancy \n\\n in Android is very broken
rtsisyk (Migrated from github.com) reviewed 2024-09-18 20:28:24 +00:00
pastk commented 2025-01-31 11:56:07 +00:00
Member
Copy link

Do I understand it right that this change is needed to generate Twine/OM strings files from existing android or ios localization files (or other twine-supported formats)?

ATM we don't use this conversion at all, only the opposite (from Twine/OM to native platform localizations).

Is there some idea to use e.g. Android -> Twine conversion?

Do I understand it right that this change is needed to generate Twine/OM strings files from existing android or ios localization files (or other twine-supported formats)? ATM we don't use this conversion at all, only the opposite (from Twine/OM to native platform localizations). Is there some idea to use e.g. Android -> Twine conversion?
rtsisyk commented 2025-02-23 10:10:11 +00:00 (Migrated from github.com)
Copy link

Do I understand it right that this change is needed to generate Twine/OM strings files from existing android or ios localization files (or other twine-supported formats)?

Yes

> Do I understand it right that this change is needed to generate Twine/OM strings files from existing android or ios localization files (or other twine-supported formats)? Yes
This repo is archived. You cannot comment on pull requests.
Reviewers
No reviewers
rtsisyk
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: organicmaps/twine#13
No description provided.
Delete branch "rdb-twine-extract"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?