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