stratos icon indicating copy to clipboard operation
stratos copied to clipboard

Languages and i18n

Open nwmac opened this issue 7 years ago • 9 comments

From @KlapTrap on November 30, 2017 13:35

  • Localise strings
  • Detect default locale
  • Change and persist locale

Copied from original issue: SUSE/stratos#14

nwmac avatar Feb 01 '18 11:02 nwmac

From @KlapTrap on January 2, 2018 14:20

https://angular.io/guide/i18n

nwmac avatar Feb 01 '18 11:02 nwmac

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

cf-gitbot avatar Feb 01 '18 11:02 cf-gitbot

Blocked on i18n changes in Angular - need ability to get translations in code, not just templates.

nwmac avatar Jun 06 '18 20:06 nwmac

i18n lookup in code is not coming until Angular V7 - Sept/Oct. We could consider using this polyfill until then - https://github.com/ngx-translate/i18n-polyfill - its by the same guy who is doing the work for Angular 7.

nwmac avatar Jun 19 '18 08:06 nwmac

Hello again.

Once again, I have been asked to localize Stratos in our project (mentioned in #4819).

May I ask, have you ever considered to use another option than @angular/localize if it's not mature enough? Some examples:

We will be forced to translate Stratos soon or later and because we have slightly extended fork of Stratos, best solution for us will be to help you translate Stratos, so our fork can be still updatable. So, if we translate Stratos, will you accept pull request? Which library should we use?

I have already tried to play with @angular/localize and noticed, that $localized captions in packages other than core (for example cloud-foundry) is not processed with ng xi18n so that's why am I suggesting alternatives.

Thanks for answer.

cache-sk avatar Jul 07 '21 12:07 cache-sk

Hello again.

Once again, I have been asked to localize Stratos in our project (mentioned in #4819).

May I ask, have you ever considered to use another option than @angular/localize if it's not mature enough? Some examples:

We will be forced to translate Stratos soon or later and because we have slightly extended fork of Stratos, best solution for us will be to help you translate Stratos, so our fork can be still updatable. So, if we translate Stratos, will you accept pull request? Which library should we use?

I have already tried to play with @angular/localize and noticed, that $localized captions in packages other than core (for example cloud-foundry) is not processed with ng xi18n so that's why am I suggesting alternatives.

Thanks for answer.

Hello Stratos Team, I have a similar problem as cache-sk, so I am waiting for answer - which way/library will be preferred....

Thanks !!!

S-logic avatar Jul 15 '21 10:07 S-logic

Hello,

We need to translate our project soon as possible, so i have a question which library we need to use? Or as @cache-sk pointed, if they translate Stratos will you accept their pull request?

Thanks a lot.

msalka avatar Jul 30 '21 10:07 msalka

Unfortunately we are not able to localise Stratos either in the short or long term. We also will not be able to provide support for the process of implementing this. In the short term (next month) we would not be able to merge and in the longer term make a release with any changes.

Also, not related to this issue, but relevant to future work, we are not able to offer support for v3 of the CF API.

richard-cox avatar Aug 06 '21 08:08 richard-cox

Hi @richard-cox thanks for answer, but.... does your statement mean that the development of the Stratos will be suspended or completely stopped ?

S-logic avatar Aug 06 '21 08:08 S-logic