> > Hmm, in which case why is it a .RTF file? After all, Rich Text
> > Format is meant to be a platform and program independant format, so
> > if your response is to limit the reading of the file to later
> > versions of Microsoft Word, would it not therefore make more sense to
> > simply save it in native Word .DOC format?
>
> You should understand that I'm not an author of RTF format, so I don't
know
> how and
> why does it work. I just know that Internet links are present in RTF since
> Microsoft
> supports Internet in Windows.
Yes, by adding customised control codes to the .RTF format and thereby
making non-standard extensions to a standardised document format! (Have you
not learned about Microsoft yet?)
> That mean both DOC and RTF files have these features.
Technically only for you.
> You can use Wordpad to read the RTF, if your Word can't do it.
> I use RTF because its functionality is 100% the same as DOC's one,
> and RTF files are 5-8 times shorter than DOC ones, since DOC uses unicode.
No, you are wrong. RTF functionality is not 100% the same as DOC
functionality. No, really, REALLY. Trust me here. Show me an RTF document
that supports revision marking, for example.
True, RTF files are 5-8 times smaller than DOC ones. This is because the RTF
files have 5-8 times less crap in them. Which in turn is because the RTF
format supports 5-8 times fewer features than the DOC format.
> I don't need unicode when writing English texts.
I take it, therefore, that you don't need to use the international
less-than-or-equal-to, greater-than-or-equal-to or not-equal symbols? Or any
number of a quite large bunch of useful symbols?
> When I write anything which contains @, it is passed as e-mail address.
I tried this. I couldn't recreate it at all.
I tried creating documents in Word, Wordpad and Notepad and loading them
into Word, Wordpad and Notepad. And not once did any of the email addresses
I put in the document have the stupid { HYPERLINK
mailto:[EMAIL PROTECTED] }codes
> That's it. I didn't know that Dave Hooper can't see this in his Word.
> What can I do? I just use Word. I don't make commercial software, so I
can't
> test
> my RTF files on each machine and read line by line to see whether it is
okay
> or not. Do you understand it? I am glad that I have Word, and I don't have
> the older
> versions. That's still the same - you blame me for something what is not
my
> fault.
You just said yourself that you have (and use) Wordpad. Why not use wordpad
to create the .RTF file in the first place?
In fact, you could even load the .RTF file into Wordpad, select all, CUT,
new document, PASTE, and then resave, to remove any strange control codes
like { HYPERLINK }
In fact, you can just load the RTF into Wordpad and then re-save it again.
When distributing documentation, you should always make sure that whoever is
receiving your software is able to actually read that documentation!
Standard .RTF format is a safe bet. As in : what Wordpad does. Not : what
Word says it does.
D a v e
