Well a +1 on behalf of my employer who loves this kind of thing.
Reading the proposal:
- How to define the primary language of the document
We have considered having a core list of languages specified at the global/service level, but it degenerates to “crazy town” mode
pretty quickly:
- If we have a fixed set of languages, then all the resources should be supporting the chosen languages, which might imply
a long interim period where configs are not consistent, wherever enabling multiple languages, or adding a new one, especially
if there are lots of layers (stats say that GeoServers installs tend to have lots of layers indeed).
- Global and different workspaces might have a different opinion about which language should be used, with possible incompatible
intersections (between global and per workspace services, if both enabled)
Rather than that, we decided to allow adding i18n per layer, and just be lenient about the language chosen, if it’s not there,
then the elements would be skipped, and if not optional (title it’s not) then the preferred language would be used, with a warning
logged so that the admin can find which layers have missing bits.
We could indeed allow the configuration of a “preferred language”… or just use the first language in the InternationalString (we
are changing it to preserve entry order from the user). Right now we are going for the latter, but maybe adding
a preferred language at the global level may not be too hard, it could be enforced in a dispatcher callback forcing
acceptLanguages to that one value if not found.
Of course, one could have a layer that still does ot have i18n or does not yet have the preferred language, in that case
a second fallback is going to be chosen (like, first entry in the i18nString)
can we just assume the primary language is english for a minimal change?
No no no no… no! The world is not that english centric, national services given the choice of just one language
use their own native language.
Any other feedback is mostly for the UI, but really it just needs to be functional:
- keywords already has some concept of language; perhaps the same UI component can be reused to prevent duplication
Considered, that component is pretty bad usability wise, we decided to let it be.
-
The list of languages for a document will all be the same (an en-CA and a fr-CA selection), may be able to help the user by adding a language to both title and abstract?
-
Abstract is often a large text area, arranging the languages along the bottom of a single text area can keep this from getting out of hand
Could be better, but we already implemented the other… Also not being able to see the various translation
at the same time seems a significant limit, parallel reading of them is important to ensure they all say the
same thing. I guess maybe you meant to have that with the “all” button? But then the component
becomes quite a bit more complicated to implement. Seems like an “exercise for the interested” to me.
Cheers
Andrea
···
== GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.