To perhaps clarify why its closed, and to try to take some heat out of the discussion, if some function is not _intended_ to work, but just happens to do so, its not a bug if it stops working.
Geany never intended to follow the Windows setting, thats why all the advice in the many issues you have referenced is always "set `LANG`". So even if somebody posted: 1. properly documented version information (top few lines of Help->debug messages) of Geany, GTK and Glib and version of Windows where it followed the Windows language settings exactly as if `LANG` was set, there are many reports of it partly following the Windows setting, but not fully so it needs careful testing, and 2. same information for the version where it doesn't, and which change between them where it failed it would still not be classified as a bug for the reason above, but if the change that stopped it working was minimal and had no other side effects it might be able to be reverted if somebody identifies it. That is why I suggested you use git bisect to identify the change. As @eht16 said, no regular Geany contributors use it on Windows much, so verifying your assertions that it used to work and now doesn't is unlikely to happen here to find what changed or to assume responsibility for guaranteeing that the feature continued to work if it was added. And making Windows specific changes is unlikely in Geany itself since nobody can test it regularly. But as noted previously on other similar issues, if somebody contributed a Windows version of the OSX startup program/script that read the Windows setting and set environment variables appropriately before calling Geany then that could probably be added to the Windows distribution (oh, and documented it so users knew how to use it :-). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2831#issuecomment-866414526
