Hello 9Val,
On Friday, July 15, 2005 you wrote:
> [-] (#0004906) Text is lost while switching between MicroEd and
> Windows style editor (in utf-8)
I believe there should be some sort of explanation for first-time
users due to microed limitations:
--you can set charset to utf-8 when using MicroEd. While this is fine,
and the message is correctly encoded, the functionality is limited
to singe codepage only. Maybe there should be some sort of indicator
telling the user "if you want to use true utf-8 with characters
truly from different codepages, you need to use windows editor".
-- if you convert from windows editor to microed, and you had unicode
characters in your message, some of them will be lost. obvious. but,
there should be a warning, and maybe there should be a way to set,
which codepage will be the resulting one (and of course, which will
be discarded).
Personally I believe the good solution of charset management is
the one in Dialog newsreader: user sets which charsets he accepts (as
a global option) and he just writes his messages. Dialog uses Windows'
information about current keyboard set and chooses the narrowest
correct charset (i.e. if you don't type any national characters, you
send us-ascii, if you use characters from just one codepage, you send
it in that codepage -- unless it is disabled in your options. if you
use many characters form different CP's -- dialog sends in unicode).
:pl-flag2:
:eu-flag2:
--
/ Krzysztof Trybowski pgp 0xE0F7733B /--/ To get my pgp key, put /
/ www.trybik.jest.okey.pl GG 1458144 /--/ "send_key" in subject. /_
:Krzysztof_Trybowski:
Using The Bat! 3.51.4 under Windows XP 5.1 build 2600.
________________________________________________________
Current beta is 3.51.3 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/
