Hey all,
today i've discovered may be a prob with file encoding (???) over a .txt file.
my pref setup is tuned to UTF-8 and a text file edited by TextMate was MacOS Roman, something to avoid definitely...
then, using another text editor i've converted this file to UTF-8 and discovered again that after having edited this file with TextMate the file becomes again in MacOS Roman...
the symtom is that TextEdit (also setup default to UTF-8) is unable to open the file.
did other get about the same prob ???
Yvon
On 15/3/2006, at 20:07, Yvon Thoraval wrote:
then, using another text editor i've converted this file to UTF-8 and discovered again that after having edited this file with TextMate the file becomes again in MacOS Roman...
How did you convert it? Most likely the file was just still in MacRoman.
You can btw convert it in the Save As… dialog of TextMate, and in Preferences -> Advanced you can set that UTF-8 should be used for existing files as well, meaning that whatever format it is loaded as, it will be saved as UTF-8.
Le 15 mars 06 à 20:13, Allan Odgaard a écrit :
How did you convert it? Most likely the file was just still in MacRoman.
No i'm sure after having converted it to UTF-8 (using SubEthaEdit) it was really in utf-8 because after that TextEdit was able to open it...
You can btw convert it in the Save As… dialog of TextMate, and in Preferences -> Advanced you can set that UTF-8 should be used for existing files as well, meaning that whatever format it is loaded as, it will be saved as UTF-8.
i've changed the popup menu in the save as dialog, the item selected was "MacOS Roman", may be that was the prob.
i'm onlu using apple + s for saving then i didn't have seen this dialog one time )))
also i didn't notice what u mentionned above (should be used for existing files as well).
thanks for your reply ;-)
Yvon
Yvon Thoraval yvon_thoraval@mac.com wrote:
Hey all,
Bonsoir Yvon,
today i've discovered may be a prob with file encoding (???) over a .txt file.
my pref setup is tuned to UTF-8 and a text file edited by TextMate was MacOS Roman, something to avoid definitely...
In "TextMate->Preferences->Advanced" have you checked "Use for existing files as well" ?
then, using another text editor i've converted this file to UTF-8 and discovered again that after having edited this file with TextMate the file becomes again in MacOS Roman...
This could have been done in TextMate as well : "File->Re-Open with Encoding..." choose "Mac-Roman" Then "File->Save As..." and check "UTF-8"
the symtom is that TextEdit (also setup default to UTF-8) is unable to open the file.
did other get about the same prob ???
Is there a curse on your machine? ;-)
At 20:07 Uhr +0100 15.03.2006, Yvon Thoraval wrote:
today i've discovered may be a prob with file encoding (???) over a .txt file.
my pref setup is tuned to UTF-8 and a text file edited by TextMate was MacOS Roman, something to avoid definitely...
then, using another text editor i've converted this file to UTF-8 and discovered again that after having edited this file with TextMate the file becomes again in MacOS Roman...
the symtom is that TextEdit (also setup default to UTF-8) is unable to open the file.
did other get about the same prob ???
Same thing here today: I've got a file that is encoded with UTF-8, but it has to be ISO-8859-1. So I select "ISO-8859-1" from the encoding menue in the "Save As" dialog. But when re-opening the file, it's still UTF-8. (Another text editor is telling me the same thing.) In Preferences -> Advanced -> Saving, I've set File Encoding to "ISO-8859-1" and "Use for existing files as well" is NOT checked because usually I don't want to change the file encoding but rather keep it the way it is.
After converting the file using Cyclone [1], everything was fine but of course I'd prefer to change the encoding in TextMate. Did I do something wrong or is this a bug?
Kind regards, Tobias
Tobias Jung newsgr@tobiasjung.net wrote:
I've got a file that is encoded with UTF-8, but it has to be ISO-8859-1. So I select "ISO-8859-1" from the encoding menue in the "Save As" dialog. But when re-opening the file, it's still UTF-8. (Another text editor is telling me the same thing.)
If you have at least one character in your file that is not in the charset you choose, then your file will be encoded as utf-8. Just find the faulty character, or decide to work with utf-8 file ;-)
At 19:44 Uhr +0100 17.03.2006, José Campos wrote:
If you have at least one character in your file that is not in thecharset you choose, then your file will be encoded as utf-8. Just find the faulty character, or decide to work with utf-8 file ;-)
Indeed! It was the endash character (option with -). I really thought that it is available in ISO-8859-1. After replacing this with the normal dash, the file wasn't saved anymore as UFT-8.
or decide to work with utf-8 file ;-)
Well, that's not up to me in this case. The project manager decided that all files have to be saved using ISO-8859-1.
Anyway, thanks a lot! :-)
Kind regards, Tobias
On 17/3/2006, at 20:00, Tobias Jung wrote:
or decide to work with utf-8 file ;-)
Well, that's not up to me in this case. The project manager decided that all files have to be saved using ISO-8859-1.
It’s not my job to meddle, but he is making a mistake, and the sooner he realizes it, the better :)
Hopefully none of the pages have forms where the user can submit data.
At 22:18 Uhr +0100 17.03.2006, Allan Odgaard wrote:
or decide to work with utf-8 file ;-)
Well, that's not up to me in this case. The project manager decided that all files have to be saved using ISO-8859-1.
It's not my job to meddle, but he is making a mistake, and the sooner he realizes it, the better :)
Since this lists can be read via a web browser, I will not reply to this. I might happen to mention that he's making even worse mistakes... oooops! ;-)
btw, Allan, could you add a warning when TextMate automatically switches to UTF-8 in such cases? I guess it's not a very important thing but it'd be nice anyway...
Kind regards, Tobias
On 17/3/2006, at 23:21, Tobias Jung wrote:
btw, Allan, could you add a warning when TextMate automatically switches to UTF-8 in such cases? I guess it's not a very important thing but it'd be nice anyway...
It is on the to-do -- it’s not that simple though, as the code that decides to fallback to UTF-8 has no ability to bring up any GUI (that’s what you get from isolating the model… ;) ).
-
Allan Odgaard -
jose.campos+tm＠galacsys.com -
Tobias Jung -
Yvon Thoraval