locale_string error due to migration from vb to dedicated server

[wrblito 0]

Hello, after migrating server files from VirtualBox FreeBSD14.0 to a dedicated FreeBSD 14.3 server, a strange problem appeared regarding the translation of locale_string by the server. As shown in the attached image, some of the texts work and translate correctly, while others are ignored.

Both servers have an identical file, byte for byte (transferred via “scp” directly from VB to the dedicated server, bypassing Windows).

The file is in the following format: locale_string.txt: Non-ISO extended-ASCII text (Windows (CR LF) ANSI) - changing it to Linux Unix did not help.

Has anyone else had this problem? It's probably a system issue, but I've been working on it for half a day already and I'm at my wits' end

I'm not sending the locale file, because if it works on VB and goes haywire on the dedicated server, it's a system issue and not a file issue.

[wrblito 0]

Fixed... it turned out that Visual Studio Code was recoding my source to UTF-8 via SFTP, which caused the characters in LC_TEXT to become garbled. After replacing it with clean source in WinMerge, everything returned to normal.