date:20220811

Re: [Geoserver-users] New OGC API Feartures dosn't support GML and HTML templates

2022-08-11 Thread Paweł Soczewski via Geoserver-users

Hi Nuno,

I did the ticket for this issue:
https://osgeo-org.atlassian.net/browse/GEOS-10619

R.
pawel

W dniu 11.08.2022 o 10:30, Nuno Oliveira pisze:
Hi Paweł,
that looks like a classpath issue, would you open up a ticket for this?

Thank you,
Nuno Oliveira

On Thu, Aug 11, 2022 at 9:09 AM Paweł Soczewski via Geoserver-users
mailto:geoserver-users@lists.sourceforge.net>>
wrote:
Hi All,

I want to move the production implementation of OGC API-Feature service
based on an early version of Geoserver 2.19.x. up to newer version.
Unfortunately both 2.20.x and 2.21.x don't support custom GML and HTML
user templates. After choosing HTML and GML encoding the server the
server responds with an error:

{"type":"NoApplicableCode","title":"java.lang.NoSuchMethodError:
org.codehaus.stax2.ri.SingletonIterator.create(Ljava/lang/Object;)Lorg/codehaus/stax2/ri/SingletonIterator;\norg.codehaus.stax2.ri.SingletonIterator.create(Ljava/lang/Object;)Lorg/codehaus/stax2/ri/SingletonIterator;"}

However custom templates for GeoJSON and JSON-LD work fine. I use the
same configuration as works fine in early 2.19.x.

When I don't use my custom GML and HTML temaplates and Geoserver uses
predefined formating, the service works fine as well.

I also tested the last version of 2.19.x with latest dedicated for it
moduls OGC API and Feature Templating and it dosen't work too but the
reason is diffrent. After instaling .jar libraries the Geoserver
application dosen't started. When delete libraries OGC API and Feature
Templating libraries it works fine.

Any idea how to fix it?

Regards,

pawel

Paweł Soczewski
Główny Specjalista ds. Infrastruktury Przestrzennej
+48502415540

GISPartner Sp. z o.o.
ul. Jana Długosza 60
51-162 Wrocław

NIP 898-20-27-647
KRS 173717
Sąd Rejonowy dla Wrocławia-Fabrycznej
VI Wydział Gospodarczy Krajowego Rejestru Sądowego
KAPITAŁ ZAKŁADOWY 1.000.000 zł

[https://www.gispartner.pl/GP-1.png]
[https://www.gispartner.pl/GP-2a.png][https://www.gispartner.pl/GP-2b.png][https://www.gispartner.pl/GP-2c.png][https://www.gispartner.pl/GP-2d.png][https://www.gispartner.pl/GP-2e.png]

___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Regards,

Nuno Oliveira

== GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information. == Nuno Miguel
Carvalho Oliveira @nmcoliveira Technical Lead / Project Manager

GeoSolutions Group phone: +39 0584 962313 fax: +39 0584 1660272
https://www.geosolutionsgroup.com/ 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.

Paweł Soczewski
Główny Specjalista ds. Infrastruktury Przestrzennej
+48502415540

GISPartner Sp. z o.o.
ul. Jana Długosza 60
51-162 Wrocław

NIP 898-20-27-647
KRS 173717
Sąd Rejonowy dla Wrocławia-Fabrycznej
VI Wydział Gospodarczy Krajowego Rejestru Sądowego
KAPITAŁ ZAKŁADOWY 1.000.000 zł

[https://www.gispartner.pl/GP-1.png]
[https://www.gispartner.pl/GP-2a.png][https://www.gispartner.pl/GP-2b.png][https://www.gispartner.pl/GP-2c.png][https://www.gispartner.

Re: [Geoserver-users] Using weblate in replacement of transifex - First feedbacks

2022-08-11 Thread Alexandre Gacon

Thank you Hans for your clear explanation. We have to check with the
developers if such changes are ok for them.

Alexandre

Le jeu. 11 août 2022 à 09:14, Hans Yperman  a écrit :

> Hello,
>
>
>
> My proposal would be:
>
>- Do a bulk-conversion with native2ascii, so all .properties files are
>ascii.
>On linux this would be something along the lines of (and presuming you
>can revert source control, the rm  might be destructive  and I did not test
>this ):
>
>
> find . -name "*.properties" -exec mv {} {}.old ";" -exec native2ascii
> {}.old {} ";" -exec rm {}.old ";"
>
>
>
>- If not enabled, you can now set
>  UTF-8
>- Use some maven plugin to enforce that *.properties is ASCII-only.
>E.g. the maven enforcer plugin, with the third party plugin for required
>encoding [1]
>
>
>
> This does a 1-shot migration to the same standard that weblate supports
> while remaining JDK8- and JDK9+ compliant.   Maven will enforce that this
> standard is followed.   As it is a mechanical translation, chances for
> breakage are minimal.
>
>
>
> Result for your concerns:
>
>- More straightforward -> you only have to use the tool once
>- Mixed standard - > After the bulk conversion and enforcement not
>anymore
>- \u escapes are less readable -> Correct, unfortunately, but only if
>your IDE guesses the encoding right, and only for western European
>languages where ISO-8859-1 is the ‘correct’ local encoding.  My personal
>experience with Dutch/French/German is that you quickly learn what each
>relevant \u is
>
>
>
> [1] https://www.mojohaus.org/extra-enforcer-rules/requireEncoding.html
>
>
>
> Hans
>
>
>
>
>
> *From:* Alexandre Gacon 
> *Sent:* donderdag 11 augustus 2022 8:04
> *To:* Hans Yperman 
> *Cc:* Jody Garnett ; geoserver-users <
> geoserver-users@lists.sourceforge.net>
> *Subject:* Re: [Geoserver-users] Using weblate in replacement of
> transifex - First feedbacks
>
>
>
> Thank you Hans for pointing me at the natice2ascii tool but I would like
> to have something more straightforward between github and the translation
> solution.
>
>
>
> For the use of not \u encoded characters I understand your point but
> currently a lot of the translations (for the most ancient ones and the most
> complete ones) are still in this case.
>
>
>
> Regards
>
> Alexandre
>
>
>
> Le mar. 9 août 2022 à 16:16, Hans Yperman  a écrit :
>
> You might be interested to know that JDK8 and lower have a tool
> native2asii that does bidirectional conversion between \u Unicode points
> and actual ISO-8859-1
>
>
>
> For JDK9+, this is deprecated/removed because JDK9 first tries to use
> UTF-8, then falls back to ISO-8859-1 if that fails.  So \u is guaranteed to
> work in both JDK8- and JDK9+, accented characters will probably work but it
> is not guaranteed (they might accidentally form a valid UTF-8 sequence).
>
>
>
> My personal experience:  The maven resource plugin defaults to the
> platform encoding e.g., when filtering is enabled, so if you don’t use \u
> there is a chance that your build randomly breaks on hosts with an UTF-8
> native encoding.
>
>
>
> See
>
>
> https://docs.oracle.com/en/java/javase/17/migrate/removed-tools-and-components.html#GUID-B49A964D-A2EF-4DAF-8A71-A64EF3E77C00
> (bottom)
>
>
> https://docs.oracle.com/en/java/javase/17/intl/internationalization-enhancements1.html#GUID-9DCDB41C-A989-4220-8140-DBFB844A0FCA
>  (bottom)
>
>
>
> Hans
>
>
>
> *From:* Jody Garnett 
> *Sent:* dinsdag 9 augustus 2022 15:53
> *To:* Alexandre Gacon 
> *Cc:* geoserver-users 
> *Subject:* Re: [Geoserver-users] Using weblate in replacement of
> transifex - First feedbacks
>
>
>
> Thanks for the experiment :)
>
>
>
> You may want to chat about this on the geoserver-devel list as it is about
> care and feeding of the codebase.
>
>
>
> I did not understand "have two different items for the same language", do
> you have an example you can link to?
>
>
>
> Jody
>
>
>
> On Mon, Aug 8, 2022 at 3:29 AM Alexandre Gacon 
> wrote:
>
> Hi all,
>
>
>
> I am studying if we could migrate the translation tooling from Transifex
> to Weblate. I have started this because with the current setup Transifex is
> changing a lot of translations when I upload updates of the translation
> source, making it difficult to do the synchronization between GitHub and
> Transifex.
>
>
>
> Weblate is a copyleft libre software and OSGeo is hosting its own
> instance, already used by several OSGeo projects (postgis, pgrouting and
> grass gis at least).
>
>
>
> Thanks to Regina Obe, I have set up a GeoServer project on the OSGeo
> instance to study how weblate works and if there is something which can
> prevent us from using it.
>
>
>
> I have already two points to share with you to get some feedback:
>
>- First, when you configure a component into weblate, you cannot have
>two items for the same language, even if they are in a different encoding.
>As a consequence, I cannot directly integrate most of the core

[Geoserver-users] Interpreting WFS parameter namesspaces

2022-08-11 Thread Ralf Trier


Hallo

the WFS 2.0 Conformance Test Suite send a request with another Namesspace then 
used in my Geoserver Project and throws an exception.

The Request:
https://host/geoserver/ps/ows?service=WFS&version=2.0.0&request=GetFeature&count=25&typenames=ns21:ProtectedSite&namespaces=xmlns(xml,http://www.w3.org/XML/1998/namespace),xmlns(ns21,http://inspire.ec.europa.eu/schemas/ps/4.0),xmlns(wfs,http://www.opengis.net/wfs/2.0)

In my geoserver project the 
namespace(-uri)/http://inspire.ec.europa.eu/schemas/ps/4.0/  has the prefix ps. 
If the prefix ps is specified in the request, the response is as expected.

Should geoserver not lookup the the namespace prefix by the namespace(-uri)?

Is this implemented and i missing sth.?

Any comments would appreciate.

 
By the way the Java-Stacktrace:

  org.geoserver.wfs.WFSException: Unknown namespace []
at 
org.geoserver.wfs.kvp.BaseFeatureKvpRequestReader.checkTypeName(BaseFeatureKvpRequestReader.java:342)
at 
org.geoserver.wfs.kvp.BaseFeatureKvpRequestReader.read(BaseFeatureKvpRequestReader.java:129)
at 
org.geoserver.wfs.kvp.GetFeatureKvpRequestReader.read(GetFeatureKvpRequestReader.java:67)
at 
org.geoserver.wfs.kvp.v2_0.GetFeatureKvpRequestReader.read(GetFeatureKvpRequestReader.java:32)
at org.geoserver.ows.Dispatcher.parseRequestKVP(Dispatcher.java:1511)
at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:684)
at 
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:261)


Thankyou.


Ralf Trier
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Pregeneralized features extension jdbcconfig compatibility

2022-08-11 Thread Alexandre Gacon

Hi everyone,

Does anyone have already used the JDBCCONFIG module with a pregeneralized
feature datastore?

The datastore uses a XML configuration file to define the different levels
of pregeneralized layers so it can be a problem no ?

-- 
Alexandre Gacon
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] New OGC API Feartures dosn't support GML and HTML templates

2022-08-11 Thread Andrea Aime

Hi Paweł,
looks like you're using two community modules
 there, the
OGC API one, and the
features templating one. The error is strange, it makes me think of a
version mis-alignment.

Just to make sure, are you using everything properly aligned, in particular:

   - OGC API and Features templating from the same version of GeoServer
   - A GeoServer 2.21.x nightly built the day as the two plugins?

Using a release of GeoServer with nightly builds of the plugins _might_
work, but might also give the results you're seeing,
if any change occurred in the middle.

If you use everything from the same build and it still occurs, it might
also be a packaging issue.
Do you have the full stack trace, from the logs?

Cheers
Andrea

On Thu, Aug 11, 2022 at 10:09 AM Paweł Soczewski via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hi All,
>
> I want to move the production implementation of OGC API-Feature service
> based on an early version of Geoserver 2.19.x. up to newer version.
> Unfortunately both 2.20.x and 2.21.x don't support custom  GML and HTML
> user templates. After choosing HTML and GML encoding the server the
> server responds with an error:
>
> {"type":"NoApplicableCode","title":"java.lang.NoSuchMethodError:
>
> org.codehaus.stax2.ri.SingletonIterator.create(Ljava/lang/Object;)Lorg/codehaus/stax2/ri/SingletonIterator;\norg.codehaus.stax2.ri.SingletonIterator.create(Ljava/lang/Object;)Lorg/codehaus/stax2/ri/SingletonIterator;"}
>
> However custom templates for GeoJSON and JSON-LD work fine. I use the
> same configuration as works fine in early 2.19.x.
>
> When I don't use my custom GML and HTML temaplates and Geoserver uses
> predefined formating, the service works fine as well.
>
> I also tested the last version of 2.19.x with latest dedicated for it
> moduls OGC API and Feature Templating and it dosen't work too but the
> reason is diffrent. After instaling .jar libraries the Geoserver
> application dosen't started. When delete libraries OGC API and Feature
> Templating libraries it works fine.
>
> Any idea how to fix it?
>
>
> Regards,
>
> pawel
>
>
>
>
> Paweł Soczewski
> Główny Specjalista ds. Infrastruktury Przestrzennej
> +48502415540
>
> GISPartner Sp. z o.o.
> ul. Jana Długosza 60
> 51-162 Wrocław
>
> NIP 898-20-27-647
> KRS 173717
> Sąd Rejonowy dla Wrocławia-Fabrycznej
> VI Wydział Gospodarczy Krajowego Rejestru Sądowego
> KAPITAŁ ZAKŁADOWY 1.000.000 zł
>
> [https://www.gispartner.pl/GP-1.png]
> [https://www.gispartner.pl/GP-2a.png][https://www.gispartner.pl/GP-2b.png
> ][https://www.gispartner.pl/GP-2c.png]<
> https://www.linkedin.com/company/gispartner/>[
> https://www.gispartner.pl/GP-2d.png]<
> https://www.facebook.com/gispartnerPL/>[
> https://www.gispartner.pl/GP-2e.png]
>
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

-- 

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

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
___

[Geoserver-users] Handbook of Geographic Information / Open Source Chapter / GeoServer DOI

2022-08-11 Thread Peter Löwe



Dear GeoServer community,

this is a follow up on the minting of a persitent Digital Object Identifier 
(DOI) for the GeoServer repository a few months back. DOI are an emerging 
standard in digital science.
This DOI reference has now been used to reference the GeoServercodebase in the 
Open Source GIS chapter of the new edition of the Springer Handbook if 
Geographic Information.
DOI can be used to reference code, data, publications and video and allow to 
give due scientific credit to the authors, in this case the project development 
team.

The Open Source GIS chapter which also covers GeoServer is available for free 
download during August 2022: 
https://link.springer.com/chapter/10.1007/978-3-030-53125-6_30.

The chapter includes also a large number of references to conference videos 
about the software tools which are adressed, which can be immediately accessed 
from the PDF.
The video references are also enabled by DOI.

Kind regards,
Peter





___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] New OGC API Feartures dosn't support GML and HTML templates

2022-08-11 Thread Nuno Oliveira

Hi Paweł,
that looks like a classpath issue, would you open up a ticket for this?

Thank you,
Nuno Oliveira

On Thu, Aug 11, 2022 at 9:09 AM Paweł Soczewski via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hi All,
>
> I want to move the production implementation of OGC API-Feature service
> based on an early version of Geoserver 2.19.x. up to newer version.
> Unfortunately both 2.20.x and 2.21.x don't support custom  GML and HTML
> user templates. After choosing HTML and GML encoding the server the
> server responds with an error:
>
> {"type":"NoApplicableCode","title":"java.lang.NoSuchMethodError:
>
> org.codehaus.stax2.ri.SingletonIterator.create(Ljava/lang/Object;)Lorg/codehaus/stax2/ri/SingletonIterator;\norg.codehaus.stax2.ri.SingletonIterator.create(Ljava/lang/Object;)Lorg/codehaus/stax2/ri/SingletonIterator;"}
>
> However custom templates for GeoJSON and JSON-LD work fine. I use the
> same configuration as works fine in early 2.19.x.
>
> When I don't use my custom GML and HTML temaplates and Geoserver uses
> predefined formating, the service works fine as well.
>
> I also tested the last version of 2.19.x with latest dedicated for it
> moduls OGC API and Feature Templating and it dosen't work too but the
> reason is diffrent. After instaling .jar libraries the Geoserver
> application dosen't started. When delete libraries OGC API and Feature
> Templating libraries it works fine.
>
> Any idea how to fix it?
>
>
> Regards,
>
> pawel
>
>
>
>
> Paweł Soczewski
> Główny Specjalista ds. Infrastruktury Przestrzennej
> +48502415540
>
> GISPartner Sp. z o.o.
> ul. Jana Długosza 60
> 51-162 Wrocław
>
> NIP 898-20-27-647
> KRS 173717
> Sąd Rejonowy dla Wrocławia-Fabrycznej
> VI Wydział Gospodarczy Krajowego Rejestru Sądowego
> KAPITAŁ ZAKŁADOWY 1.000.000 zł
>
> [https://www.gispartner.pl/GP-1.png]
> [https://www.gispartner.pl/GP-2a.png][https://www.gispartner.pl/GP-2b.png
> ][https://www.gispartner.pl/GP-2c.png]<
> https://www.linkedin.com/company/gispartner/>[
> https://www.gispartner.pl/GP-2d.png]<
> https://www.facebook.com/gispartnerPL/>[
> https://www.gispartner.pl/GP-2e.png]
>
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>


-- 

Regards,

Nuno Oliveira

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Technical Lead / Project Manager


GeoSolutions Group
phone: +39 0584 962313
fax:  +39 0584 1660272

https://www.geosolutionsgroup.com/
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.
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] New OGC API Feartures dosn't support GML and HTML templates

2022-08-11 Thread Paweł Soczewski via Geoserver-users

Hi All,

However custom templates for GeoJSON and JSON-LD work fine. I use the
same configuration as works fine in early 2.19.x.

When I don't use my custom GML and HTML temaplates and Geoserver uses
predefined formating, the service works fine as well.

Any idea how to fix it?

Regards,

pawel

Paweł Soczewski
Główny Specjalista ds. Infrastruktury Przestrzennej
+48502415540

GISPartner Sp. z o.o.
ul. Jana Długosza 60
51-162 Wrocław

NIP 898-20-27-647
KRS 173717
Sąd Rejonowy dla Wrocławia-Fabrycznej
VI Wydział Gospodarczy Krajowego Rejestru Sądowego
KAPITAŁ ZAKŁADOWY 1.000.000 zł

___
Geoserver-users mailing list

If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Using weblate in replacement of transifex - First feedbacks

2022-08-11 Thread Hans Yperman

Hello,

My proposal would be:

  *   Do a bulk-conversion with native2ascii, so all .properties files are 
ascii.
On linux this would be something along the lines of (and presuming you can 
revert source control, the rm  might be destructive  and I did not test this ):


find . -name "*.properties" -exec mv {} {}.old ";" -exec native2ascii  {}.old 
{} ";" -exec rm {}.old ";"



  *   If not enabled, you can now set   
UTF-8
  *   Use some maven plugin to enforce that *.properties is ASCII-only.  E.g. 
the maven enforcer plugin, with the third party plugin for required encoding [1]

This does a 1-shot migration to the same standard that weblate supports while 
remaining JDK8- and JDK9+ compliant.   Maven will enforce that this standard is 
followed.   As it is a mechanical translation, chances for breakage are minimal.

Result for your concerns:

  *   More straightforward -> you only have to use the tool once
  *   Mixed standard - > After the bulk conversion and enforcement not anymore
  *   \u escapes are less readable -> Correct, unfortunately, but only if your 
IDE guesses the encoding right, and only for western European languages where 
ISO-8859-1 is the ‘correct’ local encoding.  My personal experience with 
Dutch/French/German is that you quickly learn what each relevant \u is

[1] https://www.mojohaus.org/extra-enforcer-rules/requireEncoding.html

Hans


From: Alexandre Gacon 
Sent: donderdag 11 augustus 2022 8:04
To: Hans Yperman 
Cc: Jody Garnett ; geoserver-users 

Subject: Re: [Geoserver-users] Using weblate in replacement of transifex - 
First feedbacks

Thank you Hans for pointing me at the natice2ascii tool but I would like to 
have something more straightforward between github and the translation solution.

For the use of not \u encoded characters I understand your point but currently 
a lot of the translations (for the most ancient ones and the most complete 
ones) are still in this case.

Regards
Alexandre

Le mar. 9 août 2022 à 16:16, Hans Yperman 
mailto:hans.yper...@vliz.be>> a écrit :
You might be interested to know that JDK8 and lower have a tool native2asii 
that does bidirectional conversion between \u Unicode points and actual 
ISO-8859-1

For JDK9+, this is deprecated/removed because JDK9 first tries to use UTF-8, 
then falls back to ISO-8859-1 if that fails.  So \u is guaranteed to work in 
both JDK8- and JDK9+, accented characters will probably work but it is not 
guaranteed (they might accidentally form a valid UTF-8 sequence).

My personal experience:  The maven resource plugin defaults to the platform 
encoding e.g., when filtering is enabled, so if you don’t use \u there is a 
chance that your build randomly breaks on hosts with an UTF-8 native encoding.

See
https://docs.oracle.com/en/java/javase/17/migrate/removed-tools-and-components.html#GUID-B49A964D-A2EF-4DAF-8A71-A64EF3E77C00
 (bottom)
https://docs.oracle.com/en/java/javase/17/intl/internationalization-enhancements1.html#GUID-9DCDB41C-A989-4220-8140-DBFB844A0FCA
  (bottom)

Hans

From: Jody Garnett mailto:jody.garn...@gmail.com>>
Sent: dinsdag 9 augustus 2022 15:53
To: Alexandre Gacon 
mailto:alexandre.ga...@gmail.com>>
Cc: geoserver-users 
mailto:geoserver-users@lists.sourceforge.net>>
Subject: Re: [Geoserver-users] Using weblate in replacement of transifex - 
First feedbacks

Thanks for the experiment :)

You may want to chat about this on the geoserver-devel list as it is about care 
and feeding of the codebase.

I did not understand "have two different items for the same language", do you 
have an example you can link to?

Jody

On Mon, Aug 8, 2022 at 3:29 AM Alexandre Gacon 
mailto:alexandre.ga...@gmail.com>> wrote:
Hi all,

I am studying if we could migrate the translation tooling from Transifex to 
Weblate. I have started this because with the current setup Transifex is 
changing a lot of translations when I upload updates of the translation source, 
making it difficult to do the synchronization between GitHub and Transifex.

Weblate is a copyleft libre software and OSGeo is hosting its own instance, 
already used by several OSGeo projects (postgis, pgrouting and grass gis at 
least).

Thanks to Regina Obe, I have set up a GeoServer project on the OSGeo instance 
to study how weblate works and if there is something which can prevent us from 
using it.

I have already two points to share with you to get some feedback:

  *   First, when you configure a component into weblate, you cannot have two 
items for the same language, even if they are in a different encoding. As a 
consequence, I cannot directly integrate most of the core components since they 
contain 2 files for the Chinese language: is it something which can be changed? 
Which one is used by GeoServer?
  *   Second, when you change the translation of a text in weblate, it 
automatically replaces special characters by their equivalent in unicode, even 
if the character exists in the ISO-8859-1 encoding. For example:
org.geoserver.security.GeoServerAut

Re: [Geoserver-users] New OGC API Feartures dosn't support GML and HTML templates

Re: [Geoserver-users] Using weblate in replacement of transifex - First feedbacks

[Geoserver-users] Interpreting WFS parameter namesspaces

[Geoserver-users] Pregeneralized features extension jdbcconfig compatibility

Re: [Geoserver-users] New OGC API Feartures dosn't support GML and HTML templates

[Geoserver-users] Handbook of Geographic Information / Open Source Chapter / GeoServer DOI

Re: [Geoserver-users] New OGC API Feartures dosn't support GML and HTML templates

[Geoserver-users] New OGC API Feartures dosn't support GML and HTML templates

Re: [Geoserver-users] Using weblate in replacement of transifex - First feedbacks

9 matches

Site Navigation

Mail list logo

Footer information