hansva commented on issue #2814:
URL: https://github.com/apache/hop/issues/2814#issuecomment-5450381818

   Hi all,
   Attached is a small project to reproduce some of the issues:
   
[locality-issues.zip](https://github.com/user-attachments/files/31546953/locality-issues.zip)
   
   Using the UI language of English, some of the workflows will fail if you 
switch to Dutch, it is flipped the other way.
   
   Most of this can be solved by correctly specifying the group and decimal 
symbol inside the reading transforms.
   But these fields are not mandatory, or not filled in by default, so a lot of 
people will just go off the defaults that do get switched when changing 
languages. 
   
   So you could end up in a situation where everything "works on my machine" 
with `nl_BE` but then when you try to run the same workflow on a Hop Server 
running under the `en_US` locale, things start failing.
   
   I think a big part of the way forward is also in making these settings very 
visible, having hop-gui/hop-run/hop-server show what locale settings they are 
using.
   
   The ROOT fix would be to make the decimal/grouping symbols mandatory and not 
just use system defaults, but that would be a breaking change, and we would 
still need some way to define the defaults (US style vs EU style vs whatever 
other local styles are out there).
   
   As I picked up the issue yesterday, I started an initial analysis/plan of 
attack on this issue in combination with #5926, as it is a related issue. Issue 
#5598 is probably also related, but I did not include it in the initial 
investigation. The investigation can be found 
[here](https://claude.ai/code/artifact/ee2f8222-e512-4119-9867-73dd00ad370b). 
DISCLAIMER: It has been done in tandem with Claude
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to