Bugzilla – Bug 592
[HTML5 Parser] Need an easy way to export standalone translator and java source files
Last modified: 2012-11-13 21:17:14 CET
The Java source files that implement the HTML5 parser would be more useful if the Java-to-C++ translator were included as well. JST in particular has expressed a desire for mozilla-central/parser/html/Makefile.in to provide a "translate" target. I've got a patch that adds a couple of scripts to the validator.nu HTML5 parser repository. I'll submit it for your review momentarily.
Created attachment 109 [details] scripts to build/export the translator and minimal java source files into mozilla-central Henri, this patch adds a few scripts to your svn repository that export not only the minimal java source files but also the Java-to-C++ translator (as a .jar file). If the exported files were committed to mozilla-central, any Mozilla developer could hack the java parser and then easily regenerate the C++ files.
Checked in. It seems that the the .java export exports everything under impl/, which is OK but not the minimal set of files. Since the translator has LGPL-only bits and javaparser.jar is LGPL, the translator export should probably export the translator and the javaparser sources, too. However, the javaparser source archive comes with a binary-only Ant extension for interacting with Google code, and that should not go into m-c.
<! DOCTYPE html> <html dir = 'ltr' > <head> Error al analizar XML, línea 1, columna 3: The markup in the document preceding the root element must be well-formed.