http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #25 from Christopher Yeleighton
2011-08-30 13:51:39 UTC ---
Well, the original documentation now shows up in Konqueror after a little
delay, so the original failure might have been due do a network problem (e.g. a
failed script downlo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #24 from Jonathan Wakely 2011-08-30
13:27:37 UTC ---
(In reply to comment #23)
> Did you alter the Doxyfile as I described in Comment 20 here?
Comment 18, rather
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #23 from Jonathan Wakely 2011-08-30
13:25:17 UTC ---
Did you alter the Doxyfile as I described in Comment 20 here? Otherwise you're
not getting valid XHTML, and you're not getting the treeview that caused the
problem when I tested it
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #22 from Christopher Yeleighton
2011-08-30 13:10:38 UTC ---
(In reply to comment #21)
> (In reply to comment #20)
> > Please publish your result (just one page will do).
>
> I've deleted it now, you can see for yourself using the (ab
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #21 from Jonathan Wakely 2011-08-22
19:08:26 UTC ---
(In reply to comment #19)
> The Doxygen output is in HTML4.
No, it's XHTML 1.0
(In reply to comment #20)
> Please publish your result (just one page will do).
I've deleted it now
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #20 from Christopher Yeleighton
2011-08-22 19:04:50 UTC ---
(In reply to comment #18)
> the konqueror rendering problem is NOT caused by the invalid XHTML.
>
> Using the source code and doxygen config in my doxygen bug report, I chan
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #19 from Christopher Yeleighton
2011-08-22 19:03:13 UTC ---
(In reply to comment #16)
> HTML5 specifies exactly how invalid documents must be parsed (to avoid
> security issues with different user-agents parsing the same document
>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #17 from Jonathan Wakely 2011-08-22
14:27:13 UTC ---
reported upstream https://bugzilla.gnome.org/show_bug.cgi?id=657081
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #16 from joseph at codesourcery dot com 2011-08-22 13:22:55 UTC ---
On Sun, 21 Aug 2011, giecrilj at stegny dot 2a.pl wrote:
> > Also, I don't know if you are an HTML expert, I'm not,
> > but I would not be **so** sure that all the vi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #15 from Paolo Carlini 2011-08-21
21:48:14 UTC ---
If you can Jon, it would be great. I tried with the browsers I have at hand to
no avail, so far. Anyway, if trustworthy html validators report errors for the
pages generated by Doxyge
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #14 from Jonathan Wakely 2011-08-21
21:26:02 UTC ---
fine, I'll reproduce it and report a bug to Doxygen
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #13 from Christopher Yeleighton
2011-08-21 21:05:11 UTC ---
(In reply to comment #11)
> Doesn't happen here. Anyway, I still believe that a sensible way to go is
> filing a Bug Report with Doxygen.
Apparently. However, the problem
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #12 from Paolo Carlini 2011-08-21
21:04:06 UTC ---
By the way, I just tried Safari 5.1 and it also works fine for me (as long as
the above link and a few others are concerned, at least)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #11 from Paolo Carlini 2011-08-21
20:59:51 UTC ---
(In reply to comment #10)
> This is the same with Safari. Note that on both Safari and Firefox, I first
> get
> a widow as displayed in the attachment in comment #5 then the right pa
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #10 from Dominique d'Humieres
2011-08-21 20:56:00 UTC ---
> I don't know which browser you are using, but with Firefox 6 the documentation
> is definitely readable.
This is the same with Safari. Note that on both Safari and Firefox,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #9 from Christopher Yeleighton
2011-08-21 20:54:33 UTC ---
(In reply to comment #8)
> I don't know which browser you are using, but with Firefox 6 the documentation
> is definitely readable.
Konqueror 4.6
> Also, I don't know if yo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #8 from Paolo Carlini 2011-08-21
20:50:06 UTC ---
I don't know which browser you are using, but with Firefox 6 the documentation
is definitely readable. Also, I don't know if you are an HTML expert, I'm not,
but I would not be **so**
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #7 from Christopher Yeleighton
2011-08-21 20:49:10 UTC ---
(In reply to comment #4)
> Bah, in my opinion, if Doxygen otherwise suits our needs we should just keep
> using it and ask users interested in HTML Validator results to file P
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #6 from Christopher Yeleighton
2011-08-21 20:45:29 UTC ---
(In reply to comment #3)
> Of course building gcc isn't necessary to run doxygen.
>
I unpacked gcc and I said { make make doc-html-doxygen; }.
Make said "No such target."
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #5 from Christopher Yeleighton
2011-08-21 20:41:56 UTC ---
Created attachment 25069
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25069
documentation screen shot
The documentation window contains two frames: the index frame and
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #4 from Paolo Carlini 2011-08-21
20:07:27 UTC ---
Bah, in my opinion, if Doxygen otherwise suits our needs we should just keep
using it and ask users interested in HTML Validator results to file PR with
Doxygen. But certainly I don't
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #3 from Jonathan Wakely 2011-08-21
19:54:15 UTC ---
(In reply to comment #2)
> Please tell me if you find the following argument invalid:
>
> 1.
> It is the responsibility of the library to provide API documentation for the
> deve
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #2 from Christopher Yeleighton
2011-08-21 19:33:07 UTC ---
Please tell me if you find the following argument invalid:
1.
It is the responsibility of the library to provide API documentation for the
developers using the library.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50143
--- Comment #1 from Paolo Carlini 2011-08-21
15:03:38 UTC ---
And the page has been *generated* by Doxygen (1.7.4, in particular), right? So,
why do you think that, if anything, this is a libstdc++ bug?!?
25 matches
Mail list logo
