Hi Alexander!

Are= you going to use some ready framework for translations or are you going to= develop a new one?

After some previous dis= cussions, it was decided to use Angular Translate -=C2=A0https://github.com/angular= -translate/angular-translate=C2=A0

=C2=A0

It woul= d be great if the solution provided an option for quick language switching.=

The suggested pattern would be a simple la= nguage switcher on the login page.

The problem is that different languages may r= equire the variable part at different locations within the string and also = may use inclinations, so you can't just break such strings apart and tr= anslate "You have" and "new messages" separately becaus= e the translation may not just require writing it like "12 new message= s you have", but will also be different for, say, 21 and 22 messages. = At least for Russian language the latter is definitely a problem to think o= f: we'll say "=D0=A3 =D0=B2=D0=B0=D1=81 21 =D0=BD=D0=BE=D0=B2=D0= =9E=D0=95 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=95", but= "=D0=A3 =D0=B2=D0=B0=D1=81 22 =D0=BD=D0=BE=D0=B2=D0=AB=D0=A5 =D1=81= =D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=AF". I believe other Sla= vic languages, and at least German and French are also affected by similar = problems.
That also concerns your question about "common" phra= ses. What is "common" in English, may differ significantly depend= ing on context in other languages.
I implore you to not forget about suc= h peculiarities. In the past I've had issues with some software package= s whose authors didn't think about that, and it was a pain translating = those packages.

This is a great point! I wo= uld expect, in the example you provided, for the property value to be the c= omplete sentence, e.g. { new_messages: "You have {variable} new messag= es" }.=C2=A0

=C2=A0

<= span style=3D"font-family:arial;font-size:small">Derick Montague* * * * * * * * * * * * * * * = *=C2=A0

Mobile:=C2=A0= 512-609-0760

http://www.derick-montague.me

<= div dir=3D"ltr" class=3D"gmail_attr">On Mon, Feb 18, 2019 at 3:19 AM Alexan= der Amelkin <a.amelkin@yadro.com<= /a>> wrote:

H= i, Susan!

15.02.2019 23:17, susan jasinski wrote:

> I=E2=80=99d like some feedback about how to breakdown translation bund= les for the GUI.
>
> My initial thought is to create a bundle per panel since companies
> have the option to pick and choose which upstream panels they want to<= br> > use. Would this be an overwhelming amount of bundles? Does this idea > scale well as we grow the number of panels? Does this scale well as > new panels are added after existing panels have already been
> translated?
>
> In addition, there could a =E2=80=9Cglobal=E2=80=9D bundle for navigat= ion and header,
> Should this include words/phrases that are common across many panels > such as =E2=80=9Csave=E2=80=9D and =E2=80=9Ccancel=E2=80=9D?
>
> Also, should GUI notifications/messages be in their own bundle or put<= br> > into their respective panel=E2=80=99s bundle?
>
> Can you think of other factors that should guide this decision?

Are you going to use some ready framework for translations or are you going= to develop a new one?

It would be great if the solution provided an option for quick language swi= tching.

I once implemented such a solution, it used a json map of English strings t= o local strings. All translatable objects had a special class name, and the= client-side Javascript code used that class to find all to-be-translated o= bjects and on the fly changed their innerHTML using the map (saving the ori= ginal content in an object's property). The con was that the implementa= tion was only able to process simple strings and couldn't be applied to= objects containing variable text (e.g. values embedded in text like "= You have 12 new messages"). The problem is that different languages ma= y require the variable part at different locations within the string and al= so may use inclinations, so you can't just break such strings apart and= translate "You have" and "new messages" separately bec= ause the translation may not just require writing it like "12 new mess= ages you have", but will also be different for, say, 21 and 22 message= s. At least for Russian language the latter is definitely a problem
to think of: we'll say "=D0=A3 =D0=B2=D0=B0=D1=81 21 =D0=BD=D0=BE= =D0=B2=D0=9E=D0=95 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=95&q= uot;, but "=D0=A3 =D0=B2=D0=B0=D1=81 22 =D0=BD=D0=BE=D0=B2=D0=AB=D0=A5= =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=AF". I believe ot= her Slavic languages, and at least German and French are also affected by s= imilar problems.

That also concerns your question about "common" phrases. What is = "common" in English, may differ significantly depending on contex= t in other languages.

I implore you to not forget about such peculiarities. In the past I've = had issues with some software packages whose authors didn't think about= that, and it was a pain translating those packages.

As to bundling, I think that if something is shipped as a separate bundle, = can be removed or added, then the translation data must go along with the r= est of the bundle. The translation engine however must either be a separate= bundle per se or be embedded into the core of WebUI.

Alexander Amelkin