Issues
- Add Native cbi18n Support for JSON Format Resource Bundles
BOX-113Resolved issue: BOX-113 - cbi18n has non helpful errormessages when resource path is wrongBOX-102Wil de Bruin
- i18n.getCurrencySymbol is brokenBOX-84
- cbi18n is using hardcoded storages. Replace by cbstorages?BOX-70
- cbi18n : Fallback mechanism for resource selectionBOX-64
- formatRBString should not be case sensitive for key/value pairsBOX-47Resolved issue: BOX-47
- cbi18n: resource lookup hierarchicalBOX-30Resolved issue: BOX-30
- cbi18n: load resources from databaseBOX-29
8 of 8
Add Native cbi18n Support for JSON Format Resource Bundles
Won't Do
Description
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Details
Sentry
Sentry
Sentry
Created August 25, 2021 at 11:31 AM
Updated August 25, 2021 at 5:41 PM
Resolved August 25, 2021 at 5:25 PM
Activity
Show:
Jon ClausenAugust 25, 2021 at 5:41 PM
Well, so it was! Apologies.
Luis MajanoAugust 25, 2021 at 5:25 PM
This was added in v2.0
https://coldbox-i18n.ortusbooks.com/getting-started/configuration
Most i18n implementations ( https://kazupon.github.io/vue-i18n/ ) and tooling ( https://github.com/lokalise/i18n-ally ) now prefer or default to JSON or YAML formats to define i18n files. The java properties format is limited in expression and, with large translation sets, becomes increasingly difficult to edit/organize.
Add native support for JSON resource bundles. This also prevents the developer from having to write custom code to transform the properties format in to JSON formats used by front-end frameworks.