for your use case you probably don’t want any language detection to be performed anyway
Doesn't seem to be https://github.com/validator/validator/blob/master/src/nu/validator/xml/langattributes/XmlLangAttributeDroppingContentHandlerWrapper.java as a breakpoint in the startElement method for that ContentHandler doesn't get called when validating a mapml document with <mapml lang="en">, perhaps because the schema isn't one of those designated by VerifierServletTransaction.isXmlLangAllowingSchema() as allowing xml:lang, and indeed it's lang not xml:lang . But I think I will just avoid the whole issue by not adding the attribute and chalk it up to something that will no doubt become clear in time. Thanks for your advice on this! Have a great Monday December 17th (my 58th birthday, which I am taking off as a national holiday).
happy 58th!
Whoa, I set htmlParser.setMappingLangToXmlLang() from true to false and now it's validating correctly. I see in the HtmlAttributes class hixie has a note "Be careful with this class. QName is the name in from HTML tokenization." Which makes me feel like Young James Heriot (dinna mess wit sumat ye ken nawt aboot).
@prushforth heh. I wish I could claim I understand all that handling myself, but actually every time I need to mess around with it, I basically have to re-learn it all again — because I forgot whatever I had known about it from the previous time I touched it. And then after re-learning it I just forget it all again until the next time
Going a little further back in time, another example is the Microdata checker
on the other hand, the RDFaLite checker is one that I made into a separate checker but that in hindsight I could have just as well incorporated into the Assertions.java code, I guess
…because it’s much simpler than the Microdata checker, and doing much fewer checks
the XmlPiChecker is another that was a big-enough and complicated-enough chunk of code on its own to merit a separate checker
@jaimeiniesta https://github.com/validator/validator/releases/download/jar/vnu.jar will always have the latest
Hi, is it possible to use nu validator in Java, from the code level? I found this: https://vzurczak.wordpress.com/2015/03/16/validating-a-html-page-with-java/ , which has a workaround, but I was hoping there is a more straightforward and more legitimate way.... Cheers
@QMG-kazala https://gist.github.com/vincent-zurczak/23e0f626eaafab96cb32 is the straightforward way to do it, actually — not just a workaround
thx @sideshowbarker ! I've seen the corresponding blog post (https://vzurczak.wordpress.com/2015/03/16/validating-a-html-page-with-java/) but was hoping there might be a tidier way. I'll give it a try anyway as I'm testing different approaches to html5 validation at the mo :) thx again
@QMG-kazala yeah, I guess the https://github.com/validator/validator/blob/master/src/nu/validator/client/EmbeddedValidator.java code in the repo might be a better starting point than the lower-level way the person used by the person who wrote that blog post
I’ve never actually used that EmbeddedValidator.java code myself (a contributor added it), so I’m not completely certain it works as expected. But at least I can say from looking at the code, it looks like it should work
anyway, if you run into any specific problems, feel free to ping me here again
I smoke-tested the resulting image to make sure the change didn’t regress anything, but I otherwise did no testing beyond that — because I personally don’t actually use the Docker image for anything
so any of y’all who actually do use the Docker image, please try running the latest from Docker Hub and if you notice any problems, either lemme know here or else file an issue
Hi!
I have a problem validating an html file with hieroglyphs (there are many such errors, here is one of them - "Malformed byte sequence: “ba”")
The file was saved with gb2312 encoding and has the tag <meta http-equiv="content-type" content="text/html; charset=gb2312">
Hieroglyph is encoded by several bytes, but error talk about only one byte. I think it's strange.
What could be the problem?
I have a problem validating an html file with hieroglyphs (there are many such errors, here is one of them - "Malformed byte sequence: “ba”")
The file was saved with gb2312 encoding and has the tag <meta http-equiv="content-type" content="text/html; charset=gb2312">
Hieroglyph is encoded by several bytes, but error talk about only one byte. I think it's strange.
What could be the problem?
Can you point me at the URL for a document that causes the validator to emit that error message?
My initial guess is, the document is being served with a Content-Type header that has a charset parameter which is something other than gb2312
As I said earlier, I think the reason you would get that error is if the document is being served with a Content-Type header that has a charset parameter which is something other than gb2312 (or gbk)
new speaking :-)
newbie that is
your client to use is prysm?
you need to deposit 32ETH and convert it to GoETH
My question what cloud infrastructure is best to use? Any ideas on ANKR?
Thanks.
I hope your not all asleep ...
Support