2:56 a.m.
While we would like, we may not have full i18n by the time of the 1.0.0.GA.
That said, this needs to be taken into account now for some aspects as
we don't want to have to break API or even worse do some schema update
to enable i18n in a later version.
So please think of this when you deal with human-facing strings like
alert emails templates, some inventory or metrics metadata maybe ?
For the strings in the UI itself, I leave it to the developer, since we
do frequent changes in the UI it may be faster to deal with i18n at once
later.
For the strings that are directly taken from a component it would make
sense to raise a JIRA if that is not i18nized yet.
Thomas
5:11 a.m.
Two things come to my mind: logging and REST API errors.
* IIUC JBoss logging supports i18n. Am I wrong?
* Should we extend the error code pattern from logging (HAWKULAR10055)
to error responses, and have internationalized messages for them?
Le 10/06/2015 09:56, Thomas Heute a écrit :
While we would like, we may not have full i18n by the time of the 1.0.0.GA.
That said, this needs to be taken into account now for some aspects as
we don't want to have to break API or even worse do some schema update
to enable i18n in a later version.
So please think of this when you deal with human-facing strings like
alert emails templates, some inventory or metrics metadata maybe ?
For the strings in the UI itself, I leave it to the developer, since we
do frequent changes in the UI it may be faster to deal with i18n at once
later.
For the strings that are directly taken from a component it would make
sense to raise a JIRA if that is not i18nized yet.
Thomas
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
5:34 a.m.
On 06/10/2015 12:11 PM, Thomas Segismont wrote:
Two things come to my mind: logging and REST API errors.
* IIUC JBoss logging supports i18n. Am I wrong?
yes AFAIk it supports it, this is why we use an ID.
* Should we extend the error code pattern from logging (HAWKULAR10055)
to error responses, and have internationalized messages for them?
Could be a good thing, but the worry is more for end-users than developers.
Thomas
Le 10/06/2015 09:56, Thomas Heute a écrit :
>
> While we would like, we may not have full i18n by the time of the 1.0.0.GA.
>
> That said, this needs to be taken into account now for some aspects as
> we don't want to have to break API or even worse do some schema update
> to enable i18n in a later version.
>
> So please think of this when you deal with human-facing strings like
> alert emails templates, some inventory or metrics metadata maybe ?
>
> For the strings in the UI itself, I leave it to the developer, since we
> do frequent changes in the UI it may be faster to deal with i18n at once
> later.
> For the strings that are directly taken from a component it would make
> sense to raise a JIRA if that is not i18nized yet.
>
> Thomas
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
5:59 a.m.
Le 10/06/2015 12:34, Thomas Heute a écrit :
On 06/10/2015 12:11 PM, Thomas Segismont wrote:
> >Two things come to my mind: logging and REST API errors.
> >
> >* IIUC JBoss logging supports i18n. Am I wrong?
yes AFAIk it supports it, this is why we use an ID.
Perfect
> >
> >* Should we extend the error code pattern from logging (HAWKULAR10055)
> >to error responses, and have internationalized messages for them?
Could be a good thing, but the worry is more for end-users than developers.
Wouldn't an internationalized error response be useful to UI developers?
6:07 a.m.
On 06/10/2015 12:59 PM, Thomas Segismont wrote:
Le 10/06/2015 12:34, Thomas Heute a écrit :
>
> On 06/10/2015 12:11 PM, Thomas Segismont wrote:
>>> Two things come to my mind: logging and REST API errors.
>>>
>>> * IIUC JBoss logging supports i18n. Am I wrong?
> yes AFAIk it supports it, this is why we use an ID.
Perfect
>
>>>
>>> * Should we extend the error code pattern from logging (HAWKULAR10055)
>>> to error responses, and have internationalized messages for them?
> Could be a good thing, but the worry is more for end-users than developers.
Wouldn't an internationalized error response be useful to UI developers?
I guess it depends if the message ends up on the console as-is.
Thomas
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3487
days inactive
3487
days old
4 comments
2 participants
participants (2)
-
Thomas Heute -
Thomas Segismont