TextMate can display ellipses ('…', a single glyph with three dots, also known as 'horizontal ellipses') correctly when opening files with them, and when they are typed, but will replace them with '‚Ķ' (not including the single quotes) when saving files. When they are opened again '‚Ķ' will displayed in their place.
Happens with UTF-8 encoding, have not tested other encodings.
System information:
OSX El Capitan Version 10.11 (15A284) MacBook Pro (17-inch, Mid 2010) Processor: 2.66 GHz Intel Core i7 Memory: 8 GB 1067 MHz DDR3 Startup Disk: Macintosh HD Graphics: NVIDIA GeForce GT 330M 512 MB
Hello Kalcifer Kandari,
On 14 Oct 2015, at 9:53 AM, Kalcifer Kandari kalciferkandari@gmail.com wrote:
TextMate can display ellipses ('…', a single glyph with three dots, also known as 'horizontal ellipses') correctly when opening files with them, and when they are typed, but will replace them with '‚Ķ' (not including the single quotes) when saving files. When they are opened again '‚Ķ' will displayed in their place.
Happens with UTF-8 encoding, have not tested other encodings.
I use the ellipsis character extensively in my work ("alt+." on my keyboard) and I do not encounter the problems you describe.
System information:
OSX El Capitan Version 10.11 (15A284)
Latest TextMate (2.8 beta 8) here. Still on Yosemite, though.
regards, Christian
Just replicated the bug again with a clean install (including all defaults reverted), here are the exact steps to replicate (using TextMate version 2 beta 8): create new file press alt+; for the ellipses press cmd+s to save close file reopen
On 14 Oct 2015, at 10:41, Christian Rosentreter karibu@gmx.net wrote:
Hello Kalcifer Kandari,
On 14 Oct 2015, at 9:53 AM, Kalcifer Kandari kalciferkandari@gmail.com wrote:
TextMate can display ellipses ('…', a single glyph with three dots, also known as 'horizontal ellipses') correctly when opening files with them, and when they are typed, but will replace them with '‚Ķ' (not including the single quotes) when saving files. When they are opened again '‚Ķ' will displayed in their place.
Happens with UTF-8 encoding, have not tested other encodings.
I use the ellipsis character extensively in my work ("alt+." on my keyboard) and I do not encounter the problems you describe.
System information:
OSX El Capitan Version 10.11 (15A284)
Latest TextMate (2.8 beta 8) here. Still on Yosemite, though.
regards, Christian
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 14 Oct 2015, at 17:00, Kalcifer Kandari wrote:
Just replicated the bug again with a clean install (including all defaults reverted), here are the exact steps to replicate (using TextMate version 2 beta 8): create new file press alt+; for the ellipses press cmd+s to save close file reopen
Once you have saved the file, can you run this in a terminal:
xxd /path/to/file
Also, after re-opening the file, can you try use Save As… (⇧⌘S) and tell me what is shown as encoding?
Bugged: xxd '/Users/user/test.txt' > '/Users/user/xxd' Not bugged: xxd '/Users/user/test2.txt' > '/Users/user/xxd2'
After closing and opening 'test.txt' again and clicking 'File -> Save As…' turns out the encoding is 'Chinese - GB18030', even though the encoding is set to 'Unicode - UTF-8' in the settings.
What may have happened is that documents were being created by something other than TextMate with 'Western (Mac OS Roman)' encoding, but when opened with TextMate, it was not converting them to UTF-8 properly, or detecting that they had a different encoding. TextMate should detect the encoding and when saving should either convert to whatever the 'Preferences' encoding is, or save in the same encoding the file was originally opened in.
Attempted to replicate the bug with documents created in TextMate but couldn't. Created a document in another application with UTF-8 encoding, and then opened and saved in TextMate with the same encoding and it saved properly.
On 14 Oct 2015, at 11:15, Allan Odgaard mailinglist@textmate.org wrote:
On 14 Oct 2015, at 17:00, Kalcifer Kandari wrote:
Just replicated the bug again with a clean install (including all defaults reverted), here are the exact steps to replicate (using TextMate version 2 beta 8): create new file press alt+; for the ellipses press cmd+s to save close file reopen
Once you have saved the file, can you run this in a terminal:
xxd /path/to/file
Also, after re-opening the file, can you try use Save As… (⇧⌘S) and tell me what is shown as encoding?
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 14 Oct 2015, at 18:19, Kalcifer Kandari wrote:
Bugged: xxd '/Users/user/test.txt' > '/Users/user/xxd' Not bugged: xxd '/Users/user/test2.txt' > '/Users/user/xxd2'
These files are identical.
After closing and opening 'test.txt' again and clicking 'File -> Save As…' turns out the encoding is 'Chinese - GB18030', even though the encoding is set to 'Unicode - UTF-8' in the settings.
The settings is for what new files should be saved as.
Did the file you test only contain the ellipsis, or did it also contain other text?
What may have happened is that documents were being created by something other than TextMate with 'Western (Mac OS Roman)' encoding, but when opened with TextMate, it was not converting them to UTF-8 properly, or detecting that they had a different encoding. TextMate should detect the encoding
It does what it can to detect encoding, which is pretty difficult, which is why it shows a sheet and asks the user to confirm the encoding for anything but ASCII/UTF-8 or text with byte order mark or extended attribute that specify the encoding.
and when saving should either convert to whatever the 'Preferences' encoding is, or save in the same encoding the file was originally opened in.
It uses the encoding the file was opened in, and for new files, what is set in preferences.
Attempted to replicate the bug with documents created in TextMate but couldn't. Created a document in another application with UTF-8 encoding, and then opened and saved in TextMate with the same encoding and it saved properly.
OK, so right now you are unable to reproduce any bug in TextMate related to encoding?
I assume your previous instructions (below) where missing something.
On 14 Oct 2015, at 17:00, Kalcifer Kandari wrote:
Just replicated the bug again with a clean install (including all defaults reverted), here are the exact steps to replicate (using TextMate version 2 beta 8): create new file press alt+; for the ellipses press cmd+s to save close file reopen
On 14 Oct 2015, at 13:04, Allan Odgaard mailinglist@textmate.org wrote:
On 14 Oct 2015, at 18:19, Kalcifer Kandari wrote:
Bugged: xxd '/Users/user/test.txt' > '/Users/user/xxd' Not bugged: xxd '/Users/user/test2.txt' > '/Users/user/xxd2'
These files are identical.
'test.txt' and 'test2.txt' are different somehow, 'test.txt' has '‚Ķ', and 'test2.txt' has '…'. xxd doesn't think there is a difference, but QuickLook and TextMate do.
After closing and opening 'test.txt' again and clicking 'File -> Save As…' turns out the encoding is 'Chinese - GB18030', even though the encoding is set to 'Unicode - UTF-8' in the settings.
The settings is for what new files should be saved as.
Did the file you test only contain the ellipsis, or did it also contain other text?
Originally yes it did, further testing confirms this is the cause. Here are updated steps to reproduce the bug: Create a file in something other than TextMate with any name Enter any text Save with 'Western (Mac OS Roman)' encoding Open file with TextMate Press 'alt+;' for ellipses press 'cmd+s' to save close file open with TextMate, or anything that can open a text file
-
Allan Odgaard -
Christian Rosentreter -
Kalcifer Kandari