This "warning" is from your application? What does it say? As far as the <?xml version="1.0" encoding="utf-8" ?> tag is concerned this is integral to all RH8 topics. RH8 moved to using XHTML hence the different tag. Change this at your own risk but I wouldn't if you want things inside the help file to work correctly. If the question mark really is causing your build process to choke, you'll have to change the build process.
Thanks Colum, I thought that might be the case about the XML file, I'll see what the Russian team says about the build process, they're using Perforce so they may be able to make changes in the system...
I'll get back once I have more info.
The warning says:
XXX3004: Warning: xxx.htm : The HTML tag "?xml version="1.0" encoding="utf-8" ?" is not a valid HTML tag (it does not begin with an alphanumeric character).
Apparently the build objects to the first "?", this happens with every file and because of this the overall build 'fails' we have to override and mark it as 'Passed' but this is on its way to becoming a major problem. Would the folks at Adobe have insight on this?
Hi, I thought I would share this in case someone else comes to this thread searching for a solution to this error message:
The HTML tag "?xml version="1.0" encoding="utf-8" ?" is not a valid HTML tag (it does not begin with an alphanumeric character).
After upgrading my project from RH7 to RH8 (and doing some other things), when I compiled CHM I got the above error message (among others) on each and every topic. I was very confused about this, because many of the topics were absolutely identical in every way with topics in another RH8 project (I compared them using Beyond Compare, among other tools) which was not giving any error messages at compile time.
This is what I did to solve the problem:
- Close the project.
- Delete the CPD file.
- Reopen the project. I got a message that one of the topics was outside the scope of the project and would not be displayed in RH Explorer. So I re-imported that topic (which actually had been successfully imported before, but okay, whatever....)
- Fixed a broken link that I found due to another "missing" topic.
- Recompiled. No more error messages!
So, at least in my case, this error message was caused by some sort of corruption which, fortunately, was easy to fix by reimporting a topic or two.
Hope this helps someone.