Nicolas George <nicolas$george@salle-s.org> wrote:
> Warp  wrote in message <462a569d@news.povray.org>:
> >   But given that the file is in XML format it doesn't make sense that
> > it would make a difference.

> Except if the copy-paste operation is not as neutral as it should.

  How could a copy-paste operation break an XML file? (Assuming, of course,
that *everything* is copied.)

-- 
                                                          - Warp

Post a reply to this message

William Tracy <wtr### [at] calpolyedu> wrote:
> It wouldn't surprise me if Windows Notepad would decide to screw up XML 
> in some way.

  I don't think it does, but notepad sux in many other ways.

  In fact, I hate all text editors which try to be too "smart" and modify
the edited files in ways not expressly requested by the user. The worst
text editors are those where you open a file and immediately save it and
the result is different than the original. Most don't do that, but they
still add unrequested modifications automatically when you edit the file.

  I like emacs because it doesn't modify files in any way, unless
specifically instructed to do so. It will not add extra newlines unless
you tell it to, it will not add or remove tabs/whitespaces unless you
explicitly tell it to, it will not remove nor change any characters in
the file no matter how "undisplayable" they are, unless explicitly
requested. In fact, you can add almost any "undisplayable" character
easily with it, a functionality which most text editors lack. Of course
this makes it more a hacker tool than anything else, but that suits me
just fine. More than just fine.

-- 
                                                          - Warp

Post a reply to this message

Warp <war### [at] tagpovrayorg> wrote:
>   In fact, I hate all text editors which try to be too "smart" and modify
> the edited files in ways not expressly requested by the user. The worst

Agreed. A text editor should be able to display as text any file type you
throw at it, and (as you say) make no changes at all unless specified. If
you can't change ASCII or Unicode content in an arbitrary filetype then a
text editor is pretty useless I reckon.

Anyway, aside from downloading the wretched svg file, how are you guys
finding the lathe recipe?

Bill

Post a reply to this message

>   I like emacs

<asshole>
Vi ... Vi ... ViiiIIIIiii....
</asshole>

-- 
__      ___ _ _ _              _____
\ \    / (_) | (_)__ _ _ __   |_   _| _ __ _ __ _  _
  \ \/\/ /| | | | / _` | '  \    | || '_/ _` / _| || |
   \_/\_/ |_|_|_|_\__,_|_|_|_|   |_||_| \__,_\__|\_, |
                                                 |__/
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|a|f|i|s|h|i|o|n|a|d|o|@|g|m|a|i|l|.|c|o|m|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|w|t|r|a|c|y|@|c|a|l|p|o|l|y|.|e|d|u|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

You know you've been raytracing too long when you boot your computer 
with multiple OSs to see which loads the new version of POV-Ray faster.

Post a reply to this message

"Bill Pragnell" <bil### [at] hotmailcom> schreef in bericht 
news:web.462a92b3a1d76b2abb6a8b250@news.povray.org...
>
> Anyway, aside from downloading the wretched svg file, how are you guys
> finding the lathe recipe?
>

<grin>
I love it. Inkscape is sitting on my desktop for a while now, but I have not 
as yet experimented so much with it. It has a lot of nice potentialities and 
you made me aware of just another one.

Thomas

Post a reply to this message

Warp  wrote in message <462a7ade@news.povray.org>:
>   How could a copy-paste operation break an XML file? (Assuming, of course,
> that *everything* is copied.)
 
The encoding can be wrong.

The copy operation can insert strange markers (wrap indicators, for example;
it seems that it the case here).

The paste operation can re-wrap or re-indent the lines (which has no
consequence on XML validity, but can harm the result if some elements are
space-sensitive like the HTML <pre> element).

I am sure there are others possible problems.

Post a reply to this message

On Sat, 21 Apr 2007 14:23:25 -0400, Warp wrote:

> Jim Henderson <nos### [at] nospamcom> wrote:
>> [quoted text muted]
> 
>> [quoted text muted]
> 
>   But given that the file is in XML format it doesn't make sense that
> it would make a difference.

And yet it did, from the post the OP wrote - seems the copy/paste in IE7
picks up + signs used to expand/collapse portions of the document. <shrug>

Seems like braindead IE7 behaviour to me.

Jim

Post a reply to this message

Nicolas George <nicolas$george@salle-s.org> wrote:
> The encoding can be wrong.

  How?

> The copy operation can insert strange markers (wrap indicators, for example;
> it seems that it the case here).

  XML shouldn't break if extra whitespace is added between elements.

> The paste operation can re-wrap or re-indent the lines (which has no
> consequence on XML validity, but can harm the result if some elements are
> space-sensitive like the HTML <pre> element).

  I can't even begin to imagine why an SVG would contain such an element.

-- 
                                                          - Warp

Post a reply to this message

Nicolas George wrote:
> Neither solution are satisfactory. For a long time, I think that PoV is
> missing a way to cleanly deal with coincident surface: some declaration in
> the scene that says "these surfaces are *meant* to be coincident, you must
> handle them that way"

But how would it handle which texture to process first?

-- 
...Ben Chambers
www.pacificwebguy.com

Post a reply to this message

Warp  wrote in message <462b9e75@news.povray.org>:
>> The encoding can be wrong.
>   How?

The XML declaration holds an encoding indication. The editor is not supposed
to parse it, therefore it will save the file in whatever encoding it
chooses. If the two encodings are not compatible, it will break. XML files
will often be in UTF-8, and editors will often save in ISO-8859-1 or
CP-1252.

>> The copy operation can insert strange markers (wrap indicators, for example;
>> it seems that it the case here).
>   XML shouldn't break if extra whitespace is added between elements.

"Wrap indicators" are not whitespace. For example, for a long time, I had
Vim configured with "showbreak=>", which means that when a line is too long
to fit on a single terminal line, a blue ">" was displayed at the left of
the second terminal line. It breaks mouse-based copy-paste, because this
blue ">" was copied along with the text.

>> The paste operation can re-wrap or re-indent the lines (which has no
>> consequence on XML validity, but can harm the result if some elements are
>> space-sensitive like the HTML <pre> element).
>   I can't even begin to imagine why an SVG would contain such an element.

That is true for basic SVG, but with SVG+CSS, you can do a lot of things. It
is enough to have "white-space: pre" in the style for some element.

Post a reply to this message