Orange-OpenSource / Orange-OpenSource/accessibility-statement-lib-ios
Use new localizables dict format
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 0
- Forks
- 2
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Description
Today the localizables resources are based on the old format, plain text, with a key/value based pattern.
Since years, Xcode provides another format much more interesting than this "legacy" format, like the one used in OUDS, based on JSON.
We should move to this new format.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the current localizables resources in the repository and compare their plain-text key/value structure with the linked OUDS Localizable.xcstrings example. Determine which resources and loading paths require migration; the work is complete when the project consistently uses the new localizables format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- localization, mobile
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100