From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: ConTeXt beta in MikTeX
Date: Sat, 25 Dec 2010 17:12:20 +0100 [thread overview]
Message-ID: <6sinrp4iv49n$.dlg@nililand.de> (raw)
In-Reply-To: <AANLkTi=QrCjfei6DMvz-Wsv1gCKZz2BuH0HRK2QHF0PJ@mail.gmail.com>
Am Thu, 23 Dec 2010 23:46:26 +0100 schrieb Martin Schröder:
>> from what I understand WinEdt kind-of-works with Unicode (as long as
>> all the characters belong to a single codepade, it is able to save and
>> read the file as UTF-8).
> It's 2010, not 1995. Forget about editors that don't do Unicode.
> Especially if they cost money.
Even in 2010 I'm still writing only texts which need the characters
from the ansinew codepage. I don't know any language which use a
different script. In the few cases I had to insert a greek word in a
text I could use ^^-notation or \char/symbol or a transscription.
So why should I care if an editor can handle chinese or arabic?
Should I really invest a lot of time to get used to another editor
only because it has features I will probably never need?
--
Ulrike Fischer
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2010-12-25 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 11:22 barndog1946
2010-12-22 11:38 ` Hans Hagen
2010-12-22 14:32 ` Ulrike Fischer
2010-12-22 22:43 ` Martin Schröder
2010-12-23 7:33 ` Mojca Miklavec
2010-12-23 22:46 ` Martin Schröder
2010-12-25 16:12 ` Ulrike Fischer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='6sinrp4iv49n$.dlg@nililand.de' \
--to=news3@nililand.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).