This content has been marked as final.
Show 5 replies
-
1. Re: Getting Started guide 3.2 pdf file corrupt.
erik777 Jan 24, 2004 1:06 PM (in response to jzendle)"erik777" wrote:
I got error with Acrobat Reader 4 on Windows, but was able to open with Acrobate Reader 6.
On Linux I couldn't open with GGV, but could open with Mozilla's default pdf viewer. I can't figure out what program it uses, and the x-application/pdf says it just uses "default". This means, of course, that I have to download it from jboss.org every time I want to view it.
I have no idea why this document is so limited, and why someone hasn't in 1.5 months of deployment addressed these accessibility issues. -
2. Re: Getting Started guide 3.2 pdf file corrupt.
erik777 Jan 24, 2004 1:08 PM (in response to jzendle)"erik777" wrote:
I just realized that on Linux Mozilla uses xpdf to view by default. Try this if you are on Linux. -
3. Re: Getting Started guide 3.2 pdf file corrupt.
luke_t Jan 26, 2004 5:28 PM (in response to jzendle)"luke_t" wrote:
Hi,
I don't see why you have to download the file every time you want to use it. There's nothing to prevent you downloading it (with wget, for example) and viewing it on your machine.
Also, I'm using SuSE Linux 9 and it works fine with Acrobat Reader 5.05 on that.
Luke.
P.S. Could you expand on the limitations of the document please as we are looking for feedback for future versions. If there are topics you would like to see covered then it would help if you could actually say what they are. -
4. Re: Getting Started guide 3.2 pdf file corrupt.
erikt Jan 27, 2004 9:06 AM (in response to jzendle)"ErikT" wrote:
P.S. Could you expand on the limitations of the document please as we are looking for feedback for future versions. If there are topics you would like to see covered then it would help if you could actually say what they are.
Why isn't the document printable?
/Erik -
5. Re: Getting Started guide 3.2 pdf file corrupt.
luke_t Jan 27, 2004 12:35 PM (in response to jzendle)"luke_t" wrote:
Saves trees I guess...
I though you were talking about content limitations.