Thread View: comp.sys.next.misc
5 messages
5 total messages
Started by Edmund Ronald
Wed, 16 Dec 1992 22:22
Software lock-in, NeXT get a life!
Author: Edmund Ronald
Date: Wed, 16 Dec 1992 22:22
Date: Wed, 16 Dec 1992 22:22
14 lines
1048 bytes
1048 bytes
I write. I write for a living. I write on my cube, when I can. Then I have to hand the copy in to an editor. Said (human :) editor sits in front of a PC. My text is usually in French, contains all these nice accents which the french seem to need like salt and pepper. There is a DOS Ascii character set, and a Windows character set. HOW THE HELL IS ONE SUPPOSED TO MOVE TEXT TO EITHER? AM I THE ONLY MAN IN THE WORLD WHO GETS ANGRY ABOUT THIS? OH, YES, I KNOW ABOUT RTF. ON THE NEXT RTF MEANS NEXT_RTF :( ARGH. Edmund (who also happens to be a NeXT developper, but can't be bothered)
Re: Software lock-in, NeXT get a life!
Author: Thomas Funke
Date: Thu, 17 Dec 1992 17:26
Date: Thu, 17 Dec 1992 17:26
22 lines
1461 bytes
1461 bytes
In article <eronald.724544541@ruble> eronald@fml.tuwien.ac.at (Edmund Ronald) writes: > I write. I write for a living. I write on my cube, when I can. Then I have > to hand the copy in to an editor. Said (human :) editor sits in front > of a PC. My text is usually in French, contains all these nice accents > which the french seem to need like salt and pepper. > > There is a DOS Ascii character set, and a Windows character set. > > HOW THE HELL IS ONE SUPPOSED TO MOVE TEXT TO EITHER? > AM I THE ONLY MAN IN THE WORLD WHO GETS ANGRY ABOUT THIS? > OH, YES, I KNOW ABOUT RTF. ON THE NEXT RTF MEANS NEXT_RTF :( > Same with german umlauts. Did someone manage to transform NeXT-RTF to PC-RTF ? I believe it's not too difficult. -- ------------------------------------------------------------------ Thomas Funke ** E-mail: thf@zelator.in-berlin.de NeXT-Developer * Unix-Consultant ------------------------------------------------------------------
Re: Software lock-in, NeXT get a life!
Author: Eric Camps
Date: Thu, 17 Dec 1992 18:39
Date: Thu, 17 Dec 1992 18:39
38 lines
2222 bytes
2222 bytes
In article <eronald.724544541@ruble> eronald@fml.tuwien.ac.at (Edmund Ronald) writes: > I write. I write for a living. I write on my cube, when I can. Then I have > to hand the copy in to an editor. Said (human :) editor sits in front > of a PC. My text is usually in French, contains all these nice accents > which the french seem to need like salt and pepper. > > There is a DOS Ascii character set, and a Windows character set. > > HOW THE HELL IS ONE SUPPOSED TO MOVE TEXT TO EITHER? > AM I THE ONLY MAN IN THE WORLD WHO GETS ANGRY ABOUT THIS? > OH, YES, I KNOW ABOUT RTF. ON THE NEXT RTF MEANS NEXT_RTF :( > > ARGH. > > Edmund (who also happens to be a NeXT developper, but can't be bothered) In NeXTSTEP 2.1, many of our customers and I were very surprised to see that a RTF file generated on a PC (with word for instance) or on a Mac was not properly handled by Edit, neither by WriteNow, neither by WordPerfect, although the RTF format contains an information on the charSet used (ansi, mac). A solution for me was to quickly write a NS2.1 piece of software called RTFiltre.app which can translate PC/RTF and Mac/RTF, making the good character encoding translation to resolve that problem of accents. The file filtered is then correctly read by Edit, WN or WP. For RTFiltre.app, if the input is not an RTF file (say an ascii file), it uses a default conversion table that you can create yourself. Soonly (if I have time), a NS3.0 RTFiltre.app will be able to export its NeXT/RTF for PC and Mac. Idem for exporting its special ascii files. -- Eric Camps - Email/NeXTmail: ecamps@xlan.fdn.org X&LAN, 2 rue du Colisee, 33000 Bordeaux, France Voice: (+33) 56 51 04 89 Fax: (+33) 56 51 05 31
Re: Software lock-in, NeXT get a life!
Author: expovisional AndreLalonde
Date: Fri, 18 Dec 1992 07:07
Date: Fri, 18 Dec 1992 07:07
26 lines
1337 bytes
1337 bytes
In article <eronald.724544541@ruble> eronald@fml.tuwien.ac.at (Edmund Ronald) writes: > > I write. I write for a living. I write on my cube, when I can. Then I have > to hand the copy in to an editor. Said (human :) editor sits in front > of a PC. My text is usually in French, contains all these nice accents > which the french seem to need like salt and pepper. > > There is a DOS Ascii character set, and a Windows character set. > > HOW THE HELL IS ONE SUPPOSED TO MOVE TEXT TO EITHER? > AM I THE ONLY MAN IN THE WORLD WHO GETS ANGRY ABOUT THIS? > OH, YES, I KNOW ABOUT RTF. ON THE NEXT RTF MEANS NEXT_RTF :( > > ARGH. > > Edmund (who also happens to be a NeXT developper, but can't be bothered) --------------------------------- DITTO! DITTO! -Andre ( )( ) Can't even sign my name properly! ---------------------------------
Re: Software lock-in, NeXT get a life!
Author: Tom Marchioro
Date: Fri, 18 Dec 1992 23:54
Date: Fri, 18 Dec 1992 23:54
37 lines
2454 bytes
2454 bytes
In <1992Dec17.172641.1584@gamelan> thf@zelator.in-berlin.de (Thomas Funke) writes: >In article <eronald.724544541@ruble> eronald@fml.tuwien.ac.at (Edmund Ronald) >writes: >> I write. I write for a living. I write on my cube, when I can. Then I have >> to hand the copy in to an editor. Said (human :) editor sits in front >> of a PC. My text is usually in French, contains all these nice accents >> which the french seem to need like salt and pepper. >> >> There is a DOS Ascii character set, and a Windows character set. >> >> HOW THE HELL IS ONE SUPPOSED TO MOVE TEXT TO EITHER? >> AM I THE ONLY MAN IN THE WORLD WHO GETS ANGRY ABOUT THIS? >> OH, YES, I KNOW ABOUT RTF. ON THE NEXT RTF MEANS NEXT_RTF :( >> >Same with german umlauts. Did someone manage to transform NeXT-RTF to PC-RTF ? >I believe it's not too difficult. This is just one aspect of what some people like to call the "font encoding morass", a problem has has been around for some time but wasn't particularly noticeable back when computers and/or their apps didn't talk to each other much. Now that they do the different encoding schemes cause all sorts of trouble and you need all sorts of filters/translators (look for example in the "utilities" provided by TeXMenu3.0 -- itself a great app by the way --- where there are 5 or 6 such filters supplied. The font encoding problem is really a pain in the TeX world for a variety of reasons, not the least of which being that Knuth did not use a uniform scheme when he first wrote the package.) I have a copy of a long descriptive post on this issue which appeared in comp.text.tex some months ago. It dosn't offer specific solutions but does make it somewhat clearer where the problems come from. I'd be glad to E-mail a copy to anyone who wants it (reposting it in this somewhat inappropriate newsgroup seems a waste of bandwidth). Tom
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads