Improve localization support in WSO2 API-M portals

[nisan-abeywickrama]

Problem

Localization Issue in APIM Portals

The APIM portals currently do not translate all text due to missing keys and unhandled dynamic texts and error messages.

Issues:

Missing Keys: Some texts lack translation keys, so they aren’t translated.
Dynamic Texts & Errors: Runtime-generated texts and error messages aren’t managed in translations.

Solution

To fix this, we need to add missing keys to the en.json and other respective language files and support handling for dynamic and error messages in the localization.

Affected Component

APIM

Version

4.3.0

Implementation

No response

Related Issues

No response

Suggested Labels

No response

[nisan-abeywickrama]

Complete the localization support work in the admin portal.

The work included adding keys and support for dynamic texts throughout the portal. In addition, added MUI component localization support as well.

[nisan-abeywickrama]

Complete the localization support work in the devportal.

[nisan-abeywickrama]

Progress - Started working on localization support for publisher portal.

Completed adding localization to Create API and API comments flow.

[nisan-abeywickrama]

Completed adding localization support to publisher portal in API level.

Todo: Add localization to global policies and identify missing localization in new UI components

[nisan-abeywickrama]

Completed the localization support work in the publisher portal

[nisan-abeywickrama]

Closing this issue as all related PRs are merged