OASIS Open Document Format for Office Applications (OpenDocument) TC

Hello all, You must be wondering what the email deluge of yesterday was all about. I added the past versions of the ODF specification to the SVN repository. This resulted in more than 50 emails, because each SVN commit leads to an SVN commit. Now I've added a first branch for a JIRA issue to SVN. I've chosen a simple issue: https://issues.oasis-open.org/browse/OFFICE-3755 This issue requires only a text change to two words. So the SVN diff does not add a lot to this issue, but it is a nice and simple example. To create the patch you can use the tool 'odftc' that is available from here: https://gitlab.com/odfplugfest/odfhistory/blob/master/odftc/odftc Then, in an empty directory, I ran these commands: == odftc init cd office odftc create v1.2 3755 vi v1.2/OpenDocument-v1.2-part1/content.xml git commit -a -m 'Change rotate-angle to skew-angle in the decription of skewX and skewY.' git svn dcommit == Now the change can be seen at this link: http://tools.oasis-open.org/version-control/browse/wsvn/office/?op=comp&compare%5B%5D=%2Fbranches%2Fv1.2&compare%5B%5D=%2Fbranches%2Fv1.2_OFFICE-3755 This is a long link, but to adapt it for other issues of v1.2, only the issue number needs to be changed. I added this link to the issue itself. Note that I edited the specification content.xml with a text editor. It is also possible to use LibreOffice, OpenOffice, WebODF or OpenExchange and then create a diff on the .odt files with OdfHistory. For now, I suggest to use simple text editors. Best regards, Jos van den Oever

Jos, How do you suggest we capture the JIRA Issue number or should we continue to enter links to the JIRA issue in the edited content.xml? I have a slight preference for the JIRA links in the text because they should be easy enough to remove later and it enables readers to go quickly from the current content to the issue that was resolved there. Thanks for all the hard work! Patrick On 10/14/2015 06:48 AM, Jos van den Oever wrote: Hello all, You must be wondering what the email deluge of yesterday was all about. I added the past versions of the ODF specification to the SVN repository. This resulted in more than 50 emails, because each SVN commit leads to an SVN commit. Now I've added a first branch for a JIRA issue to SVN. I've chosen a simple issue: https://issues.oasis-open.org/browse/OFFICE-3755 This issue requires only a text change to two words. So the SVN diff does not add a lot to this issue, but it is a nice and simple example. To create the patch you can use the tool 'odftc' that is available from here: https://gitlab.com/odfplugfest/odfhistory/blob/master/odftc/odftc Then, in an empty directory, I ran these commands: == odftc init cd office odftc create v1.2 3755 vi v1.2/OpenDocument-v1.2-part1/content.xml git commit -a -m 'Change rotate-angle to skew-angle in the decription of skewX and skewY.' git svn dcommit == Now the change can be seen at this link: http://tools.oasis-open.org/version-control/browse/wsvn/office/?op=comp&compare%5B%5D=%2Fbranches%2Fv1.2&compare%5B%5D=%2Fbranches%2Fv1.2_OFFICE-3755 This is a long link, but to adapt it for other issues of v1.2, only the issue number needs to be changed. I added this link to the issue itself. Note that I edited the specification content.xml with a text editor. It is also possible to use LibreOffice, OpenOffice, WebODF or OpenExchange and then create a diff on the .odt files with OdfHistory. For now, I suggest to use simple text editors. Best regards, Jos van den Oever --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau

Hello Patrick, I changed the subject to get the attention of the TC members. On Wednesday 14 October 2015 17:44:01 Patrick Durusau wrote: > How do you suggest we capture the JIRA Issue number or should we > continue to enter links to the JIRA issue in the edited content.xml? > > I have a slight preference for the JIRA links in the text because they > should be easy enough to remove later and it enables readers to go > quickly from the current content to the issue that was resolved there. I see that you have added links like these in the places where you made a change: <a href=".../OFFICE-3876">OFFICE-3876</a> (I left out namespaces and some attributes) These are indeed easy to remove. I have not added them in the example I gave. I think this is a good point to ask opinions of the TC. The SVN tracks where an issue was changed, but it is not easy to insert the link to the JIRA issue automatically. It's not possible to link every JIRA issue, because some issues give changes in places that do not allow links. Some options: - Add JIRA issues numbers in place. Pro: easy to navigate from text to JIRA issue Con: is usually inline with the text which makes the diff larger. - Maintain a changelog with applied JIRA issues. This can also be created later from the commit history. In my opinion, it is useful to add the JIRA links where possible. > Thanks for all the hard work! You're welcome. I'm happy I finally made the commits instead of continiuing to polish the XML of the older specification files. Cheers, Jos