Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CLOSED] Turkish UTF-8 characters not saved properly #2516

Open
core-ai-bot opened this issue Aug 29, 2021 · 2 comments
Open

[CLOSED] Turkish UTF-8 characters not saved properly #2516

core-ai-bot opened this issue Aug 29, 2021 · 2 comments

Comments

@core-ai-bot
Copy link
Member

Issue by peterflynn
Wednesday Jan 23, 2013 at 20:29 GMT
Originally opened as adobe/brackets#2643


@nusu I've filed this bug on your behalf and deleted the wiki page you created. Please report issues here in the future.

Bug report from@nusu:

hello, i just downloaded brackets and my idea is very good and fast, but i saw anything soo badly, it isn't save as utf-8 i am using turkish keyboard and i have ş,ç,ö,ğ,ü,ı this code editor doesn't save that. for example: http://prntscr.com/oeua3

@core-ai-bot
Copy link
Member Author

Comment by RaymondLim
Thursday Jan 24, 2013 at 19:21 GMT


I don't think we have enough (or correct) information in the description or in the linked page. Brackets does support those characters from Turkish keyboard layout if you have utf-8 encoding specified in your html page (ie. you have <meta charset="utf-8">). However, if you have non-utf-8 encoding, then Brackets won't handle those characters (not just Turkish characters, but also other high-ascii or double bytes characters). This is a known issue and we already have a Trello card for this.

@core-ai-bot
Copy link
Member Author

Comment by peterflynn
Thursday Jan 24, 2013 at 23:10 GMT


@nusu: It sounds like you might have been working with a file that wasn't actually encoded with UTF-8, since Raymond's testing seems to show that Turkish chars work fine in Brackets with UTF-8 files.

Assuming that's what happened, we have a user story to support other encodings that's already tracking this issue -- so I'll close the bug here.

Please ping us back if you think this is in error (for example, if you check the problem file's encoding and it really is UTF-8). We can reopen this bug if so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant