For now we are using InternationalString to follow our best practice for human readable text.
If you read the ticket the wish is to find resources (perhaps you have time?) to allow this value to be internationalized. At least the API is in place so the work can be performed :) -- Jody Garnett On Jun 9, 2023 at 6:28:24 AM, Dieter Stüken - con terra GmbH via Geoserver-devel <geoserver-devel@lists.sourceforge.net> wrote: > Message Title > > Great! > > this was a badly missed feature. > > > > I was busy with other projects some time, so I missed the discussion about. > > > > Currently, our planning software uses the translated description of > attributes as attribute name. > > Those may contain special characters which confuses SLD and possibly gets > misinterpreted as CQL expression. > > > > I noticed a discussion about using a GrowableInternationalString. > Entering it manually, the locale becomes Locale.getDefault(). Setting it > via REST I guess I may user different locales. Can I use even several ones? > Which one is the default, the first one? > > Which one is chosen? Does it depend on the browser settings? > > > > .. I just give it a try. > > > > Dieter. > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
