A good example of how ISO fails to encourage harmonized standards. These function definitions would be perfect for reusing in a variety of other standards, or at least for harmonizing with other standards that also define scientific functions, like ISO/IEC 29500 and ODF 1.2’s OpenFormula. But even peer standards professionals in other ISO committees and liaisons are not given free access to these standards. We would need to pay over $100 for the privilege of volunteering to write better ISO standards.
“I’d take all the source code for OpenOffice and print it out onto paper. Then I’d erase it from the repository. I’d store the paper print-outs at the top of a tower, surrounded by an alligator filled swamp, fifty miles from the development lab.
Sure, the developers can re-use that old code, I’ve no problem at all – It’s just got to be worth the effort of walking to the swamp, wading through the murky waters, wrastling the ‘gators, climbing the tower and copying the source out by hand. If they’re not willing to do that, then that code just isn’t worth it.
Next I’d go way back to basics – take something like CKEditor as my base, then look at what I’d need to do to make it produce ODF.”
“La librairie iTools, librairie sous licence GPL, développée par l’équipe d’Itaapy, offre de nombreux outils permettant de faciliter l’internationalisation.
Grâce à ces outils, il est possible de traduire très rapidement un document ODF (ODT/ODS/ODP). Le principe est simple et tient en 3 étapes !”