Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #58218

Re: RTF vs XCode

Show all headers | View raw

Tim Streater wrote:
> ErikRS <mac-dane@is.invalid> wrote:
>> Tim Streater wrote:
>>> Your Name <YourName@YourISP.com> wrote:
>>>> 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.
>>>
>>> Well obviously. A .tiff is a different format from a .jpg or .png and
>>> the file sizes will be diffeent too.
>>>
>>> A .txt file is just text. So is a .rtf file. You can save your text
>>> file as .doc but that doesn't make the file be in Word format. Try
>>> writing some simple text in a Word document, save it as .doc, and open
>>> that with BBedit and see how far you get.
>>
>> Exact this method I've used many, many times when people came to me
>> with more or less damaged .doc/.docx files which they aren't able to
>> open in Word (mainly Word for Windows).
>
> Even when the .doc file contains tables, footnotes, styled text (such
> as italics or bold), headings, paragraph spacing, different fonts and
> points sizes, and so on? You trying to pretend that this information
> can be manipulated by native BBedit? (I know nothing of these plugins
> of which you speak)
>
> You might be able to manage some of that with a .docx file, which AIUI
> is in XML, and therefore when opened by a text editor will appear as
> text, and which you stand some chance of being able to edit without
> destroying it.
>
> The only circumstance in which you might manage it with a .doc file,
> which is a binary format, is if the author used Word as a text editor -
> didn't use any tables, footnotes, styled text (such as italics or
> bold), headings, paragraph spacing, different fonts or points sizes. A
> circumstance in which, IOW, the author might as well have used a text
> editor to prepare the text, but didn't. The text in such a file is
> usually quite visible.
>
>> The most obvious differences are all the crap that MSWD puts into the
>> document header and each and everytime you've hit the 'Save' command.
>
> This "crap" as you so wittily describe it, is where the formatting
> information about tables, footnotes, styled text (such as italics or
> bold), headings, paragraph spacing, different fonts and points sizes is
> stored.

I did as I wrote with both .doc, .docx and .rtf files. The thing is that 
when you know /which/ things to remove and not to remove or insert, then 
you will keep any formattings as in the original documents.

At that time when I did most of these rescues I used OS X 10.2.8 and 
later 10.3.x, since many of the old plug-ins are/were written in carbon 
and most of them worked with BBEdit 6.x and some even with BBEdit Lite 
6.1.x.

I've also pulled out data using BBEdit 6.x from some Filemaker databases 
needed at a hospital here. - Infact it was a matter of life and death 
for the doctor to get these informations. I know this case was not a 
normal case. The doctor and the developer of the FMP databases had a 
conflict, and the developer denied to make the base as the doctor would 
have it and he - the developer - locked the base, so the doctor couldn't 
access it. So he called me and gave me the backup CDs and luckily I 
could pull out the needed data.

So yes, BBEdit can be used for quite more than one should expect... And 
to strip a .doc file for MS crap is far much easier than you could think 
of. The header info in a MSWD .doc file doesnot contain informations 
about fonts, sizes, styles etc.. These informations are saved along with 
each paragraph.

Each time such a Word file is saved it will inlay new header 
informations both at the top and at the place, where it was saved along 
with information about operating system, appiication version, dates and 
time etc.etc... If you just remove all that crappy stuff and leave the 
style informations untouched and save the stripped file as a .rtf file, 
you can just open it in the word processor of your own choice.

In the 'late night' document mentioned it was my own fault that I had to 
replace some odd characters with the correct Danich ones was that I 
forgot to change the read method in BBEdit from ASCII to UTF. I was 
first aware of this today when I tried the various savings. BBEdit 
always opens in ASCII mode and not the document's mode...

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

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