|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello,
It took some time, but I've finally packaged the TrainFaces macro and
uploaded it to the object collection. This is the same macro I used to
make the faces in the post http://news.povray.org/48458c33%40news.povray.org
If anyone tries it, any feedback or suggestions on the macro or
documentation is welcome, as always.
--
-The Mildly Infamous Blue Herring
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Blue Herring" <pov### [at] bherringcotsenet> wrote in message
news:48863da6@news.povray.org...
> Hello,
> It took some time, but I've finally packaged the TrainFaces macro and
> uploaded it to the object collection. This is the same macro I used to
> make the faces in the post
> http://news.povray.org/48458c33%40news.povray.org
>
> If anyone tries it, any feedback or suggestions on the macro or
> documentation is welcome, as always.
> --
> -The Mildly Infamous Blue Herring
Hi,
When I tried opening the various html files using Internet Explorer 7 under
Windows the images and links didn't work. I believe the issue was down to a
tag 'base href="."' that Open Office seems to have inserted into the header
section of each file. I removed this line from each of the html files on the
web site and they now seem to work ok under both Firefox and IE7 on Windows.
You might want to check that they're still ok when viewed from Linux. I
don't know if you have an option under Open Office to suppress the offending
tag in the future.
When I did get to see all those chubby smiling faces, I couldn't help
breaking out in a stupid smirk myself. It looks like you've done a really
nice job there.
Regards,
Chris B.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris B wrote:
> When I tried opening the various html files using Internet Explorer 7
> under Windows the images and links didn't work. I believe the issue was
> down to a tag 'base href="."' that Open Office seems to have inserted
> into the header section of each file. I removed this line from each of
> the html files on the web site and they now seem to work ok under both
> Firefox and IE7 on Windows. You might want to check that they're still
> ok when viewed from Linux. I don't know if you have an option under Open
> Office to suppress the offending tag in the future.
>
> When I did get to see all those chubby smiling faces, I couldn't help
> breaking out in a stupid smirk myself. It looks like you've done a
> really nice job there.
Heh, thanks very much!
I really appreciate you making those corrections. As a rule I always do
my HTML by hand, but this time I thought I'd try OpenOffice with the
XHTML export. I really like OpenOffice, and the XHTML export does work
quite well. However, there are some small but crucial details that
can't be controlled from within the application. For example, it
completely refused to output relative link urls. Additionally it output
utf8 characters instead of entities for things like non-breaking
space, and left/right quotes, which gave me mime errors on upload. So
the final result still needed to be run through a sed script and Tidy.
I'm pretty sure this issue isn't tweakable from within the application
either. So it was a good experience until the end, and the next version
I'll probably be doing by hand, or possibly with some custom xslt.
<potential rant>
As an aside, I manage the internal web site for my group at work, and I
must say IE has been the bane of my existence. I do it by hand with
some custom XML and XSLT and am a stickler for making it 100% standards
compliant. However its amazing in how many wacky ways IE can break
things, requiring painful tweaking...
</potential rant>
Just curious, is there a specific reason why HTML needs to be ASCII
instead of utf8 for the collection?
--
-The Mildly Infamous Blue Herring
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Blue Herring" <pov### [at] bherringcotsenet> wrote in message
news:48874f80$1@news.povray.org...
>
> I really appreciate you making those corrections. As a rule I always do
> my HTML by hand, but this time I thought I'd try OpenOffice with the XHTML
> export. I really like OpenOffice, and the XHTML export does work quite
> well. However, there are some small but crucial details that can't be
> controlled from within the application.
I usually do it by hand too but I tend to end up with fairly bland looking
results. I've tried Microsoft Office in the past and really didn't like the
generated html. I recently loaded a copy of OpenOffice and I was planning to
play around to see how that does at generating html with sophisticated
layout.
> Just curious, is there a specific reason why HTML needs to be ASCII
> instead of utf8 for the collection?
When setting up the site we were asked to check that text format files only
contained ASCII characters. I don't recall any real discussion over it at
the time. I think there is some sense to it being ASCII though as UTF8 might
imply that using extended character sets is encouraged.
ps. I'm not convinced that very many people monitor this newsgroup
regularly, so you might want to add a little response to the existing thread
in povray.binaries.images.
Regards,
Chris B.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris B wrote:
> I usually do it by hand too but I tend to end up with fairly bland
> looking results. I've tried Microsoft Office in the past and really
> didn't like the generated html. I recently loaded a copy of OpenOffice
> and I was planning to play around to see how that does at generating
> html with sophisticated layout.
It does quite well, though there's always the arm-wrestling that goes
on. I would recommend the XHTML export rather than saving as the
HTML/text format, it does a much better job of preserving the
formatting. Just don't expect it to respect all the settings that would
apply to the HTML/text format. A few other things I learned, fields
generally don't export, if you add images make sure they are linked,
hidden text fields turn into comments (but not hidden paragraphs.)
> When setting up the site we were asked to check that text format files
> only contained ASCII characters. I don't recall any real discussion over
> it at the time. I think there is some sense to it being ASCII though as
> UTF8 might imply that using extended character sets is encouraged.
Well, an explosion of different character sets wouldn't be great, so I
guess that keeps everything compatible.
> ps. I'm not convinced that very many people monitor this newsgroup
> regularly, so you might want to add a little response to the existing
> thread in povray.binaries.images.
OK, I'll do that, thanks for the tip.
--
-The Mildly Infamous Blue Herring
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|