Re: [NTG-context] New Release Winedt WORKS with MKIV!!
On Sun, 21 Nov 2010 02:03:33 -0700, barney schwartz
New build of WinEdt 6.0 (Build: 20101121) has been uploaded to
www.winedt.com
This build contains macros that work with the latest ConTeXt Mark IV (previous versions were designed for older version of ConTeXt). If you are upgrading from older version of WinEdt make sure that the executable for ConTeXt in WinEdt's Execution Modes is set context.exe (instead of old texexec.exe)...
I used winedt for years, and turning it into a full-fledged dedicated ConTeXt editor would not be hard ... I had to leave it because there was no utf-8 or bidi support. limited utf-8 is now available -- so interesting that Aleks made MkIV default --, don't know when/if-ever bidi support will be there ... otherwise the best dedicated tex editor I've ever used... Best wishes Idris -- Professor Idris Samawi Hamid, Editor-in-Chief International Journal of Shiʿi Studies Department of Philosophy Colorado State University Fort Collins, CO 80523
2010/11/23 "\"Idris Samawi Hamid ادريس سماوي حامد\"" wrote:
I used winedt for years, and turning it into a full-fledged dedicated ConTeXt editor would not be hard ... I had to leave it because there was no utf-8 or bidi support.
limited utf-8 is now available -- so interesting that Aleks made MkIV default --, don't know when/if-ever bidi support will be there ...
I don't know if bidi will ever be there either, but the sole fact that it supports UTF-8 is already surprising (the editor lags behing for ages in that respect) and enough for a vast majority of TeX users. It's not that he made it default on his own machine - it is now default with every installation of WinEdt (it might be that they made that on his request). Mojca
Am Tue, 23 Nov 2010 19:43:13 +0100 schrieb Mojca Miklavec:
limited utf-8 is now available -- so interesting that Aleks made MkIV default --, don't know when/if-ever bidi support will be there ...
I don't know if bidi will ever be there either, but the sole fact that it supports UTF-8 is already surprising (the editor lags behing for ages in that respect) and enough for a vast majority of TeX users.
The limited utf-8-support has been there for years. And it is really very limited: WinEdt is not capable to handle utf-8 documents that require more than one code page (eg. a mix of Russian and French). I don't care very much as I'm not using other scripts. In the few cases I need access to chars from other codepages I can use ^^^^-notation. Or use emacs. -- Ulrike Fischer
On Thu, Nov 25, 2010 at 11:01:17AM +0100, Ulrike Fischer wrote:
Am Tue, 23 Nov 2010 19:43:13 +0100 schrieb Mojca Miklavec:
limited utf-8 is now available -- so interesting that Aleks made MkIV default --, don't know when/if-ever bidi support will be there ...
I don't know if bidi will ever be there either, but the sole fact that it supports UTF-8 is already surprising (the editor lags behing for ages in that respect) and enough for a vast majority of TeX users.
The limited utf-8-support has been there for years. And it is really very limited: WinEdt is not capable to handle utf-8 documents that require more than one code page (eg. a mix of Russian and French).
I've seen all sorts of limited unicode support, but that one is really retarded, I can't actually imagine how such thing would be coded! Regards, Khaled -- Khaled Hosny Arabic localiser and member of Arabeyes.org team Free font developer
Am Thu, 25 Nov 2010 12:31:05 +0200 schrieb Khaled Hosny:
limited utf-8 is now available -- so interesting that Aleks made MkIV default --, don't know when/if-ever bidi support will be there ...
I don't know if bidi will ever be there either, but the sole fact that it supports UTF-8 is already surprising (the editor lags behing for ages in that respect) and enough for a vast majority of TeX users.
The limited utf-8-support has been there for years. And it is really very limited: WinEdt is not capable to handle utf-8 documents that require more than one code page (eg. a mix of Russian and French).
I've seen all sorts of limited unicode support, but that one is really retarded, I can't actually imagine how such thing would be coded!
It is a simple mapping to a 256 codepage: To quote from the documentation: However, WinEdt can transparently convert Unicode (UTF-8) documents into ACP when they are loaded and back to UTF-8 when they are saved. This makes it possible to work with UTF-8 documents as long as they can be converted into ACP (Ansi Code Page). -- Ulrike Fischer
participants (4)
-
"\"Idris Samawi Hamid ادريس سماوي حامد\"" -
Khaled Hosny -
Mojca Miklavec -
Ulrike Fischer