TÜRKCE KARAKTER SORUNU YETER YAV CÖZÜMÜ YOK MU

Sanane Kurt

kodlama yapıyorum sürekli korce de kalıyor türkce karakter sorunu var her seferinde yeni bir txt actıgımda veyada yeni bir c++ dosyası actıgımda kodlamadan türkce windows-1254 secmek zorunda kalıyorum ve düzenleme bittikten sonra kaydet dedigimde yine korece olarak başlıyor cözümü nedir bunun ayarladıgım kodlama dilinde kalmıyor

PeterJones

@Sanane-Kurt ,

I am coding and it always stays in Korean. I have a Turkish character problem. Every time I open a new txt or a new c++ file, I have to select Turkish windows-1254 from the coding. After editing is finished, when I click save, it starts in Korean again. What is the solution for this? It does not stay in the coding language I set?

Notepad++ has a feature where it can try to guess the encoding; unfortunately, there is NO reliable way, by looking at the bytes of a Windows text file, to tell for sure what the encoding of the file is – the best any program can do is to guess, and it sometimes gets it wrong.

Settings > Preferences > MISC > ☐ Autodetect character encoding controls that behavior. If it’s not on, you might see if turning it on helps Notepad++ to guess properly. If it is on, then Notepad++ is not guessing properly, so try turning it off; you might also need to make sure that Settings > Preferences > New Document > Encoding is set to your Windows-1254 encoding.

But neither setting is a guarantee that Notepad++ will guess correctly. The fundamental problem is that when the DOS filesystem (FAT) was being decided upon in the 80s, they didn’t bother storing meta-information about file encoding and the like, and that decision from 45 years ago propagated to the FAT32 (USB drives) and NTFS (modern Windows filesystem) as well. Because that metadata isn’t included, there is no way for any application to know for sure, and there’s nothing Notepad++ can do about the underlying filesystem.

That said, in the 90s, this cool thing called “Unicode” was invented, along with the UTF-8 encoding, which can, with a single file encoding, represent more than 1,000,000 characters.

Notepad++ supports UTF-8 encoding (and the related UTF-16 encodings), which give you full access to Unicode. If you were just using the files in Notepad++, there is no reason to use any non-Unicode encoding (like Windows-1254), because UTF-8 will represent all the Turkish characters and all the Korean characters separately, without ambiguity, so there would never be any conflict. Further, you say you are “coding”, and I haven’t heard of any modern compiler that would understand a 256-character encoding like Windows-1254 but not also handle UTF-8. If you do everything in UTF-8, there will be no difficulty with encoding.