ruby-i18n / ruby-i18n/ruby-cldr
Export `alt` attribute consistently
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 78
- Forks
- 18
- Avg merge
- 9d 8h
- Merged PRs (30d)
- 3
Description
CLDR has an alt attribute that can be used to indicate a different things:
alt=proposed\d*andalt=#{variantname}-proposed\d*indicate proposed values that will replace the non-altversion of the value. They will always have adraftattribute, since as soon as they get theacceptedstatus, the non-altversion is replaced.alt=#{variantname}indicates an alternative value that really ought to be used in specific conditions.
Currently, ruby-cldr filters out values with an alt attribute in some places using the Base#alt? method. However, it's inconsistently applied.
We might want to export data with alt=#{variantname} style attributes, perhaps using a separate key name. cldr-json does this:
<language type="en_US">Engels (VSA)</language>
<language type="en_US" alt="short">Engels (VSA)</language>
gets exported as:
"en-US": "Engels (VSA)",
"en-US-alt-short": "Engels (VSA)",
Contributor guide
No contributing guide indexed for this repository
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 tracing where ruby-cldr applies Base#alt? and comparing the affected exports with the CLDR XML and cldr-json examples in the issue. Define how alt=#{variantname} values should be represented separately from the base value, then verify that proposed values remain handled consistently across the export paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100