[mkgmap-dev] [mkgmap-svn] Commit r4822: - use StandardCharsets.US_ASCII instead of "ascii" parameter where possible

Wed Dec 1 13:04:53 GMT 2021

Hi Ticker,

seems the problem was somewhere else, with r4825 everything looks okay.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap at jagit.co.uk>
Gesendet: Mittwoch, 1. Dezember 2021 13:05
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] [mkgmap-svn] Commit r4822: - use StandardCharsets.US_ASCII instead of "ascii" parameter where possible

Hi Gerd

I don't understand either why CommonHeader change caused problem.

There is a slight difference in the handling of
   String(xx, "charSetName")
and
  String(xx, actualCharSet)
in that the second replaces unmapable chars and won't throw an
exception.

Ticker

On Wed, 2021-12-01 at 11:37 +0000, Gerd Petermann wrote:
> Hi Ticker,
>
> thanks for the hint. I did not see that Integer.parseInt() also
> handles a null value.
> I still don't understand why I also had to revert the change in
> CommonHeader :(
>
> Gerd

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev