Hi,
Will there be more text encoding support? Like for Japanese(Shift- JIS), Chinese(GB-2312) or Korean? I think this issue has been bought up before, but it didn't get my attention until lately.
I have been working on websites in different language: Chinese, Japanese and Korean, and it was a horrible experience. I had to add some pages to the existing websites, so i can't really changed all the text encoding to unicode. Also, I have been told that there are some missing characters in unicode for Japanese, so even the government won't use that.
My nightmare stopped when bbedit came to rescue, it supposed all of the text encoding I need. But then I want to stick to Textmate, and, well, bbedit is simply far too expensive!
My guess is that I will need to maintain those websites in the future, so it will be great to see textmate supporting more text encoding!
Thanks
Kelvin
On 12/3/05, Kelvin Tse post@ktml.net wrote:
Will there be more text encoding support? Like for Japanese(Shift- JIS), Chinese(GB-2312) or Korean? I think this issue has been bought up before, but it didn't get my attention until lately.
I'm pretty sure Allan has shot this down in the past, its just not something trivial to do, and Unicode does its job perfectly well.
I have been working on websites in different language: Chinese, Japanese and Korean, and it was a horrible experience. I had to add some pages to the existing websites, so i can't really changed all the text encoding to unicode. Also, I have been told that there are some missing characters in unicode for Japanese, so even the government won't use that.
The government is a terrible measure to do anything by, especially in the world of computers.
-- --Robert Deaton http://somethingunpredictable.com
Will there be more text encoding support? Like for Japanese(Shift- JIS), Chinese(GB-2312) or Korean? I think this issue has been bought up before, but it didn't get my attention until lately.
I'm pretty sure Allan has shot this down in the past, its just not something trivial to do
Allan didn't shoot it down -- he said something like 'it's on the list but not in the immediate future'.
and Unicode does its job perfectly well.
Unicode in TM *doesn't* work perfectly well for Japanese because:
(a) You can't do text input at all for Japanese even in Unicode (b) Japanese text is not displayed as double-width so the characters appear to overlap and look 'squished' together.
I think this is true for other multibyte languages too but I can only comment on Japanese for which TM is simply not usable :-(
Until TM supports non-western languages, the best I can recommend is to register a copy of skEdit for $20 which is a close runner-up to TM in that it's a very nice tabbed interface done in Cocoa. Not as drop- dead beautiful or feature-rich as TM, but pretty dang good and handles multibyte languages including Shift-JIS without a hitch. Beats the bejeezus out of bbedit --eewwww!
Happy coding!
Sean
:::: DataFly.Net :::: Complete Web Services http://www.datafly.net
Sean Schertell wrote:
Unicode in TM *doesn't* work perfectly well for Japanese because:
(a) You can't do text input at all for Japanese even in Unicode (b) Japanese text is not displayed as double-width so the characters appear to overlap and look 'squished' together.
I believe the second problem is not with Unicode, but with the font you are using. Unicode is only a way to represent characters in bits and bytes (actually, that's UTF-8's job and Unicode only defines the numbers). It is not Unicode's job to display them.
It *is* also possible to do Unicode Japanese input in TextMate, but you're not gonna like it… OS X contains a "Unicode Hex" inputmethod. With this inputmethod, if you press option, you can type the hexadecimal value of the Unicode codepoint and you get the character typed...
This is probably not workable, but there is at least one way to do it..
Jeroen.
Unicode in TM *doesn't* work perfectly well for Japanese because: (a) You can't do text input at all for Japanese even in Unicode (b) Japanese text is not displayed as double-width so the characters appear to overlap and look 'squished' together.
I believe the second problem is not with Unicode, but with the font you are using. Unicode is only a way to represent characters in bits and bytes (actually, that's UTF-8's job and Unicode only defines the numbers). It is not Unicode's job to display them.
Understood. My point was just that when someone said earlier that TM works fine with unicode for East Asian languages, it doesn't.
It *is* also possible to do Unicode Japanese input in TextMate, but you're not gonna like it… OS X contains a "Unicode Hex" inputmethod. With this inputmethod, if you press option, you can type the hexadecimal value of the Unicode codepoint and you get the character typed...
For the love of god... kill me now! :-)
Sean
:::: DataFly.Net :::: Complete Web Services http://www.datafly.net
I just tried skEdit, I think I like it, it's very ftp oriented, and it display the right!(Works with Japanese and Korean, but not chinese through, i think it's a bug in the program). I think I will buy a register it. :) It gonna help me a lot.
Thanks Sean
Kelvin
On 04/12/2005, at 11:31 AM, Sean Schertell wrote:
Will there be more text encoding support? Like for Japanese(Shift- JIS), Chinese(GB-2312) or Korean? I think this issue has been bought up before, but it didn't get my attention until lately.
I'm pretty sure Allan has shot this down in the past, its just not something trivial to do
Allan didn't shoot it down -- he said something like 'it's on the list but not in the immediate future'.
and Unicode does its job perfectly well.
Unicode in TM *doesn't* work perfectly well for Japanese because:
(a) You can't do text input at all for Japanese even in Unicode (b) Japanese text is not displayed as double-width so the characters appear to overlap and look 'squished' together.
I think this is true for other multibyte languages too but I can only comment on Japanese for which TM is simply not usable :-(
Until TM supports non-western languages, the best I can recommend is to register a copy of skEdit for $20 which is a close runner-up to TM in that it's a very nice tabbed interface done in Cocoa. Not as drop-dead beautiful or feature-rich as TM, but pretty dang good and handles multibyte languages including Shift-JIS without a hitch. Beats the bejeezus out of bbedit --eewwww!
Happy coding!
Sean
:::: DataFly.Net :::: Complete Web Services http://www.datafly.net
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
I just tried skEdit, I think I like it, it's very ftp oriented, and it display the right!(Works with Japanese and Korean, but not chinese through, i think it's a bug in the program). I think I will buy a register it. :) It gonna help me a lot.
being based on NSTextView (OS X native text component), skEdit inherits all the goods and the evils of it :) that is, you have chinese support but I guess you cannot have snippets ^_^
being based on NSTextView (OS X native text component), skEdit inherits all the goods and the evils of it :) that is, you have chinese support but I guess you cannot have snippets ^_^
It's true that skEdit uses OS X's text component which makes it (IMHO) a bit inferior to TM for western language code editing. But just so ya know, it does actually have snippets :-)
Sean
:::: DataFly.Net :::: Complete Web Services http://www.datafly.net
On Dec 3, 2005, at 5:22 AM, Kelvin Tse wrote:
Will there be more text encoding support? Like for Japanese(Shift- JIS), Chinese(GB-2312) or Korean? I think this issue has been bought up before, but it didn't get my attention until lately.
[The most recent word I can find about this from Allan in the archives is from July: ...
I'm going to add better/actual international support to TM eventually. Though currently it looks a little like it'll be a 1.4- thing (but 1.2 and 1.3 should take shorter time than the current 1.1).
...]
I have been working on websites in different language: Chinese, Japanese and Korean, and it was a horrible experience. I had to add some pages to the existing websites, so i can't really changed all the text encoding to unicode. Also, I have been told that there are some missing characters in unicode for Japanese, so even the government won't use that.
The potential number of these characters is vast. Shift-JIS, for example, doesn't include all of them either, and does have a number of variants and ambiguities that Unicode does not have. There are political reasons one might not want to use Unicode, but not having "all" Japanese kanji probably isn't a valid one (for recent versions of Unicode, at least).
Chris