Re: texteditors that can process and save in different encodings

From: alka irani <alka.irani_at_gmail.com>
Date: Mon, 8 Oct 2012 07:52:22 -0400

नमस्ते !

namaste !

I have worked mostly on GNU/Linux and Indian languages. I found Openoffice
to be the best editor on Desktops/laptops for complex scripts which works
on GNU/Linux as well as Windows. All that one has to have is the Opentype
Font corresponding to the script of the language and an input scheme (
keyboard) for the script enabled at Operating system level.

I have also used a very simple freely downloadable editor yudit in which
you can write simple text without formatting.
This text can then be copied / pasted in openoffice or any other
program/application like gmail/chat etc.

For any support, you can send me an e-mail on irani.alka_at_gmail.com

अलका ईरानी

On Sun, Oct 7, 2012 at 9:27 PM, Doug Ewell <doug_at_ewellic.org> wrote:

> [image: Boxbe] <https://www.boxbe.com/overview>
> unicode-bounce@unicode.org is not on your Guest List<https://www.boxbe.com/approved-list>| Approve
> sender <https://www.boxbe.com/anno?tc=12601219191_105425078> | Approve
> domain <https://www.boxbe.com/anno?tc=12601219191_105425078&dom>
>
> Stephan Stiller wrote:
>
> Ideal would be an editor that gives me previews in an easy-to-use
>> encoding selection menu that in addition highlights fully or almost-
>> compatible encodings, highlights (after loading) positions in the file
>> that don't conform to the requested encoding (and lets me choose how
>> to handle them), and knows different versions of encodings.
>>
>
> I once tried an editor that had something like this, but it was otherwise
> so unsuitable that I don't even remember its name any more.
>
> As some codepages had minor additions or corrections in later
>> versions, it'd be useful to have an editor that offers the choice to
>> access earlier versions of encodings - this is clearly specialist
>> usage but the knowledge exists.
>>
>
> Most character sets change very little, at least in terms of repertoire,
> and the changes are almost always limited to adding new characters. A
> feature to access earlier versions of encodings would probably have only
> the effect of disallowing characters that were added in later versions,
> replacing them with question marks or U+001A. Even for character-set wonks
> like us, it's hard to see that being useful in a practical sense.
>
> --
> Doug Ewell | Thornton, Colorado, USA
> http://www.ewellic.org | @DougEwell ­
>
>
>

-- 
ई.अलका
Scientist
- Joint Director ( Language Computing Group till 30th April 2012)
- Convener, Maharashtra, Gujarat, Goa of
  Consortium of Scientists for Sustainable
  Development
- Rajyogini at Brahmakumaris, Gamdevi Centre
- Director(hon), Social welfare, Bharati Samskrit
  Vidya Niketanam
Received on Mon Oct 08 2012 - 06:58:51 CDT

This archive was generated by hypermail 2.2.0 : Mon Oct 08 2012 - 06:58:53 CDT