The article you refer to is “applicable” to any XML format that you know well. E.g., you could save your 10 ODTs into FOTDs, then do the modifications (provided that you know what’s wrong there - just the same way the author of the article knew what describes the boxes, and if they need them or not).
But note that the article didn’t discuss why author had to use the XML editing tool in the first place. Because the same problem (multiple invisible boxes in the ODS) may be solved from UI - using Navigator (F5
), you may see the drawing objects there, double-click each to select it, and Del
to remove. The only reason to use direct XML editing is to do a mass-removal (test with bug document in tdf#130326 to see the problem described in that article).
Generally - you need to know the format very well yourself to be able to “optimize” that way.