Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.system > #58208
| From | ErikRS <mac-dane@is.invalid> |
|---|---|
| Newsgroups | comp.sys.mac.system |
| Subject | Re: RTF vs XCode |
| Date | 2014-03-29 12:49 +0100 |
| Organization | solani.org |
| Message-ID | <lh6c0t$t09$1@solani.org> (permalink) |
| References | <chine.bleu-DE94A3.20260927032014@news.eternal-september.org> <290320140844592292%YourName@YourISP.com> <lh4t1v$a2s$1@solani.org> <280320142306408124%timstreater@greenbee.net> <290320141224355373%YourName@YourISP.com> |
Your Name wrote: > Tim Streater <timstreater@greenbee.net> wrote: >> ErikRS <mac-dane@is.invalid> wrote: >>> Yes, BBEdit is the ultimate text editor. It has no direct saving >>> functionality into /any/ file format. But it handles plain and styled >>> text and it can be used for editing RTF and other files, because it >>> always keeps the primary format as the saving format. I.e. if you open a >>> TXT file in BBEdit and use the COM+S, it will keep the .txt format, and >>> if you open a RTF file, hit COM+S it will keep the .rtf format >>> >>> Another benefit is that BBEdit can save directly into customized >>> formats. I.e. if you open a TXT file (or any other file format), make >>> your changes and select 'Save As' you can change the suffix from .txt to >>> .rtf, .doc, docx etc, and the saved tocument will be a document of the >>> chosen file format. - And hereto fully formattings are kept as the >>> original an d it's possible to add styled text to a .txt file! >>> >>> Just tried with a RTF file which I first saved as a TXT file - all >>> formattings are kept, - and then again back to a TXT file - all >>> formattings are kept. >> >> You seem to be implying that BBedit knows how to save a text file in >> Word format. RTF is just text, nothing special about it. Some >> applications will *interpret* it as styled text, but that's a different >> story. >> >> Changing the suffix doesn't change the file format. It just changes the >> suffix. The file content is unaltered. > > I don't know about BBEdit, but GraphicConverter is definitely "suffix > aware" - when in a Save As window, whatever suffix you type on the > filename will automatically change the file format it saves as (as will > choosing the format from the pop-up menu of course). If you type ".jpg" > or ".jpeg" the file saves as a JPG. If you type ".tiff" it saves as a > TIF, etc. And it's exactly the same way BBEdit reacts for most file formats. There are still formats that BBEdit can't handle without a plug-in installed. I've just now tried it out once more... Opened a blank BBEdit file, put some text - this answer - into it and hit the 'Save As'. There is no suffix specified in the titlebox. - First when you enter a suffix and save the file, it will be associated to be the selected file format, - and it works! Another of the old-timers - Tex-Edit Plus - handles it in another way. Here you need to use 'Save As' and select the file format you need to use... Cheers, Erik Richard -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Erik Richard Sørensen, Member of ADC, <mac-daneRE@MOVEstofanet.dk> NisusWriter - The Future In Multilingual Text Processing - www.nisus.com Openoffice.org - The Modern Productivity Solution - www.openoffice.org ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Back to comp.sys.mac.system | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
RTF vs XCode Siri Cruise <chine.bleu@yahoo.com> - 2014-03-27 20:26 -0700
Re: RTF vs XCode Jolly Roger <jollyroger@pobox.com> - 2014-03-28 04:11 +0000
Re: RTF vs XCode Siri Cruise <chine.bleu@yahoo.com> - 2014-03-27 23:35 -0700
Re: RTF vs XCode ErikRS <mac-dane@is.invalid> - 2014-03-28 14:30 +0100
Re: RTF vs XCode Siri Cruise <chine.bleu@yahoo.com> - 2014-03-28 06:39 -0700
Re: RTF vs XCode Your Name <YourName@YourISP.com> - 2014-03-29 08:41 +1200
Re: RTF vs XCode Your Name <YourName@YourISP.com> - 2014-03-29 08:44 +1200
Re: RTF vs XCode ErikRS <mac-dane@is.invalid> - 2014-03-28 23:28 +0100
Re: RTF vs XCode Tim Streater <timstreater@greenbee.net> - 2014-03-28 23:06 +0000
Re: RTF vs XCode Your Name <YourName@YourISP.com> - 2014-03-29 12:24 +1200
Re: RTF vs XCode Tim Streater <timstreater@greenbee.net> - 2014-03-29 08:02 +0000
Re: RTF vs XCode ErikRS <mac-dane@is.invalid> - 2014-03-29 13:17 +0100
Re: RTF vs XCode Tim Streater <timstreater@greenbee.net> - 2014-03-29 18:02 +0000
Re: RTF vs XCode ErikRS <mac-dane@is.invalid> - 2014-03-30 03:00 +0200
Re: RTF vs XCode Your Name <YourName@YourISP.com> - 2014-03-30 09:55 +1200
Re: RTF vs XCode Tim Streater <timstreater@greenbee.net> - 2014-03-29 22:27 +0000
Re: RTF vs XCode ErikRS <mac-dane@is.invalid> - 2014-03-30 03:16 +0200
Re: RTF vs XCode ErikRS <mac-dane@is.invalid> - 2014-03-29 12:49 +0100
Re: RTF vs XCode ErikRS <mac-dane@is.invalid> - 2014-03-29 12:30 +0100
Re: RTF vs XCode Your Name <YourName@YourISP.com> - 2014-03-29 12:03 +1200
Re: RTF vs XCode Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-03-28 23:56 +0000
Re: RTF vs XCode Your Name <YourName@YourISP.com> - 2014-03-29 12:20 +1200
Re: RTF vs XCode ErikRS <mac-dane@is.invalid> - 2014-03-29 12:55 +0100
Re: RTF vs XCode Your Name <YourName@YourISP.com> - 2014-03-29 12:27 +1200
Re: RTF vs XCode Your Name <YourName@YourISP.com> - 2014-03-29 12:32 +1200
csiph-web