From: Julio S. <jul...@gm...> - 2005-07-02 19:25:57
|
2005/7/2, Alex Roitman <sh...@gr...>: > Julio, >=20 >=20 > It opens fine in my OOo, screenshot here: > http://gramps-project.org/source/shots/shot.png >=20 > My OOo is 1.1.4-3 from Debian unstable. Good to know, it seems to affect OOo 2.x only. The file is broken. This I have seen. So it has to be fixed in GRAMPS, at least until it produces DTD-conforming files. Now, OOo 2.x is broken, it is unacceptable for any program to die this way, especially a program that might be fed data not built by its user. There may be a security hole hidden there. So they have to fix it until it does no die. Now, simple-minded cleanup of the XML does not keep that small file from breaking OOo. The question is: is the result of the cleanup a completely legal OOo file, or is it still broken? Who will need to run this last mile? Is the new OOo broken if it does not take the file, or has GRAMPS always produced broken output and the old OOo was more permissive? That, I do not know yet. Julio |