|
|
Posted by Athel Cornish-Bowden on 08/24/07 09:00
On 2007-08-23 23:55:07 +0200, dorayme <doraymeRidThis@optusnet.com.au> said:
> In article <5j56teF3sd08cU1@mid.individual.net>,
> Athel Cornish-Bowden <athel_cb@yahoo.co.uk> wrote:
>
>> On 2007-08-22 22:56:47 +0200, dorayme <doraymeRidThis@optusnet.com.au> said:
>>
>>> In article <5j2up4F3ovuhqU1@mid.individual.net>,
>>> Athel Cornish-Bowden <athel_cb@yahoo.co.uk> wrote:
>>>
>>>> On 2007-08-22 12:15:59 +0200, dorayme <doraymeRidThis@optusnet.com.au>
>>>> said:
>>>>
>>>>> Safari does not happily negotiate
>>>>>
>>>>> http://tinyurl.com/24y5hp
>>>>>
>>>>> iCab is quite simply brilliant, FF is fine. I don't know about
>>>>> IE6 and 7, Mac IE is fine too.
>>>>>
>>>>> I was surprised by Safari, make the window not too big and see
>>>>> how it fails to show some of the links.
>>
>> [ ... ]
>>
>>> OK, now, this out of the way, you likely have a Mac. So how about
>>> confirming or giving me your observations about Safari please n
>>> respect of above.
>>
>> I'd be glad to do so, but your URL gives a 404 error today (both on
>> Safari and on iCab) though it worked yesterday. Have you moved the test
>> page?
>
> After it was pointed out to me in quite unparliamentary language
> that the source code formatting was not the best, I took it down,
> stormed off and got blind drunk. I am out on bail now and will
> see if I can see what the problem is. (It has been confirmed by a
> spider and me already that Safari likes ids in tds rather than
> trs if you read the thread. But thanks Athel.
Now it loads fine. In iCab the links work perfectly (with highlighting)
even when the window is small. Safari (2.0.4, i.e. the version that
came with my computer, now almost two years old) does a much worse job,
as you say, and not all links work. If I click on #RA_TK6, for example,
it fails to take me there, and I need to scroll.
>
> Talk to me about formatting instead,
The formatting looks just fine if I get iCab to display the source (or
Safari, Mozilla 1.7.3 or Firefox 1.5.0.3) for that matter), but if I
download your file and look at the source with TexEdit it looks a mess.
However, if I select Quick cleanup --> LFs-->CrRs (Unix-->Mac) in
TexEdit's tools menu then it gets formatted perfectly. I don't usually
go through this exercise with my own source code, because if I want to
tinker with it I go back to the original file as it was before it got
uploaded to a server running Unix. However, if I do do it (for example
with http://bip.cnrs-mrs.fr/bip10/homepage.htm) then the result is more
or less the same as with yours, in other words the formatting gets
screwed up and needs to be cleaned up before it will display properly
on the Mac.
> I am desperately at sea
> about how to set my text editor
I don't remember which editor you said you used (BBEdit?), but anyway,
it wasn't TexEdit. TexEdit (not to be confused with Apple's rudimentary
TextEdit, incidentally) is the only editor I normally use, but I
imagine other good editors offer the same Unix-->Mac conversion that
TexEdit does.
> and/or my Cyberduck ftp program
> and/or how much blame to apportion my server host. What are the
> general causes of something looking mighty fine on the screen in
> a text editor only to see later in the source code of some (I
> emphasise some) of my website pages, no gaps between lines that
> were there before, various bits bunched together and so on and so
> forth. Perhaps my editor is too good and complicated and I am
> lost in the variables of the enormous list of preferences.
As suggested above, I think the problems arise when it gets uploaded,
and there is probably nothing to do in the editor file. In any case,
the formatting looks fine if I display the source in any of the four
Mac browsers that I have installed (see above -- I used to have IE, but
I seem to have dumped it at some point), and that is all one normally
needs to do. Browsers don't care about formatting of source files, so
the only person who really needs to understand your source is you. If
others want to loook at it then they need to use a browser that
displays it properly. Maybe this is one of the things that Mac users
take for granted and that Windows users imagine to be impossible.
--
athel
Navigation:
[Reply to this message]
|