If not PDF, then I'd certainly be willing to pay for an additional manual (Eovia did this also with Carrara) If UT would author a PDF manual then we'd be able to print it if we like, load it on a Kindle and read it offline, all while having a functioning table of contents and references / index pages. Unfortunately, Unity doesn't provide a structured offline manual. I realize this takes time to create - any comprehensive documentation takes time to create.įortunately Unity has a decent amount of online documentation. The PDF format is a very rich and powerful format that when used as intended, offers the reader of the document a lot of powerful >search, bookmarking, markup< and other advanced features which can be taken advantage of. I'm asking for a manual here - there's a difference.Įovia (when they existed) created a PDF manual for Hexagon that even embedded video tutorials! There's no table of contents, cross referencing - is that really a manual or simply a print out? Sure I could print to PDF a continuous swath of html text but then I could also fill up Notepad with 100k of text and print that to PDF as well.īoth yeilds the same kind of unorganized document with no cross references, indexing or anything that considers the quick, methodological lookup of information. When a document is authored with PDF in mind it usually includes a table of contents which is functional and can be clicked, taking you straight to the subjects within. Then there are people (like me) who prefers to (also) be able to read their manual offline, away from the computer. There are those people who can comfortable work with a program and switch back and forth between the application and help window. But as I had stated elsewhere, the more complex a program is, you'd think that a manual would be a requirement. I can (almost) understand saving money by not printing manuals.
No malice but I have to say I don't understand why excuses are always offered for a program when users simply request offline documentation?
0 kommentar(er)
