Start enabling i18n for metadata with Ext I18N

Description

Patch Bahmni Core to make it support i18n for metadata. This support will be conditional to Ext I18N being loaded and started.
Possible metadata:

  • Address entries

  • Patient identifier types

Activity

Show:
Dimitri Renault
December 20, 2017, 4:59 PM

PR #24 submitted.

  • BAH-317: I18N support when searching by identifiers and address fields values.

Angshuman Sarkar
January 23, 2018, 9:07 AM

Can you articulate with example usages please?

Darius Jazayeri
May 4, 2018, 11:28 PM

I know you two have discussed this offline. Can you give a quick update here on what the next steps are?

Dimitri Renault
May 5, 2018, 6:25 AM

We have agreed on a more general approach obfuscating the specifics of how i18n is handled behind reusable interfaces. Basically using Ext I18N would be one possible implementation amongst possible others.
In the meantime we have identified possible new areas of development on Ext I18N, and we would like to go through that first before resuming its integration in Bahmni Core.

I would like to keep working on this ticket and have transitioned it to 'In analysis' for now.

angshuman sarkar
March 31, 2020, 9:33 AM

closing this card. I think the PR was withdrawn by you as well. Create a new thread/card if needed.

Incomplete

Assignee

Dimitri Renault

Reporter

Dimitri Renault

Labels

Units

None

PercentDone

None

DueTime

None

Clients

None

External issue ID

None

UAT Assignee

None

Reviewer

Angshuman Sarkar

Sprint

0.93 Product M3

Fix versions

Configure