From: Adam 

Frank Haber wrote:
> The question: What trouble can a modern Linux/BSD user get into with
> line endings, config files and ASCII/UNICODE flavor?
>
> The back story: I remember, from pre-history, these:
>
> o ^Z EOFs completely bollix old MS linkers.
> o Mac CR EOLs are poison in UNIX config files.  PC CRLFs just make the
> parsers stop cold.
>
> Recently, on the NT board:
>
> I find that XP notepad handles big-endian UTF-16 fine, and WordPad does
> not, or possibly interprets as some Asian alphabet.  I'm not about to
> try REGEDIT import.
>
> So the questions are, I guess:
>
> 1. What kind of trouble can I get into on modern Linux....blah, blah
> (see first line).
>

Most of the files I've played with have been good to go on both. Maybe I'm
just lucky or maybe there is something built into Linux which assumes
windows eol's are to be expected.

> 2. I have a couple of dragondrop utils on NT that can fix line endings.
> Drop a file thereon; follow prompts to strip CRs, convert to Mac, etc.
> Ever seen a similar filter for Linux?  One that knows about Unicode 8/16
> and byte order? And one for Win that knows Unicode?\
>

Yes.....but I'm not on my linux machine at the mo. I think most of the
actual text editors do this (e.g. Kate)


> 3. My UltraEdit 12 on Win can output any of the above, and more.  Is
> there a Pico-ish editor for UNIX that can do the same?  Vi and Emacs
> need not apply.
>
> -joe user

Yes there is. & there are Java editors which can run on both & handle either.

Adam

--- BBBS/NT v4.01 Flag-5