has anyone found a work around this bug? because my application needs to produce a pdf file that has special characters like <.. which aurigadoc catches as a start of an tag.. does anyone have the same problem?
and btw,, can a CHM be produce via web application, if so, how? i tried to copy and paste my source code in a desktop (which is working) then give the correct input output path.. but nothing works (in the web app)... anyone?
Log in to post a comment.