Closed BlackMage2 closed 2 years ago
Do you have an example NFO? iNFekt tries to fix umlauts in some cases, but CP437 (the classic NFO charset) does NOT support umlauts...
here(in the zip, sry nfo is not allowed): new 20.nfo[ISO-8859-1 or ISO-8859-15 is the correct encoding, but in Notepad++ it is also wrongly auto recognized as OEM-US]
Well, if this is still relevant, you could change the encoding/charset in the status bar. Just right click the field on the the far right and choose "Windows-1252". Works for me with your nfo:
well, I didn't know that
For me, where there is usually an umlaut, only 'ⁿ' should appear. also instead of 'für' only 'fⁿr'. Umlauts should be supported in nfo files, right?