[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [oic] Version Control Commit by bart.hanssens - file names of advisories
I'm confused by the name change. I think there are two separate issues. One is not about hiding tracked changes so much as extracting in-line text (which will exclude tracked changes). It looks like the problem first seen is related to doing that incorrectly (and a bug in the list of exceptions to in-line text). This applies to many other situations. Another is about what to do when tracked-changes are not supported and whether producers that do not support tracked changes should preserve the text:tracked-changes element and the markers that show up in the character data of the in-line text. It would be valuable to deal with these as a pair, not as one. I haven't looked closer, but the name change seems to invite treating them together. - Dennis -----Original Message----- From: Hanssens Bart [mailto:Bart.Hanssens@fedict.be] Sent: Wednesday, June 16, 2010 03:48 To: dennis.hamilton@acm.org; oic@lists.oasis-open.org Subject: RE: [oic] Version Control Commit by bart.hanssens - file names of advisories Ok, thanks, I've added the link to the JIRA issue. I've also moved the result files to a subdirectory and renamed the HTML file containing the description and the directory itself (but used the name hiding_tracked_changes, pointing to the end the result of the issue, rather than the cause in-line-text-extraction) Best regards Bart ________________________________________ From: Dennis E. Hamilton [dennis.hamilton@acm.org] Sent: Monday, June 14, 2010 9:15 PM To: oic@lists.oasis-open.org Cc: Hanssens Bart Subject: RE: [oic] Version Control Commit by bart.hanssens - file names of advisories I think adding a structured name is all right, but I would do it differently. For me, I would rather see 00001-in-line-text-extraction.html To give a clue to what this is about. And maybe, if not otherwise apparent, we should say 00001-ODF1.1-5.1-inline-text-extraction.html To zero in on where the omission occurs and where an extraction procedure can capture inappropriate material. In case I didn't mention it already, there is now an ODF TC JIRA Issue OFFICE-2706 on this issue: <http://tools.oasis-open.org/issues/browse/OFFICE-2706>. You may find it interesting that current ODF 1.2 drafts eliminate the distinction of in-line text from other text altogether. - Dennis -----Original Message----- From: workgroup_mailer@lists.oasis-open.org [mailto:workgroup_mailer@lists.oasis-open.org] Sent: Monday, June 14, 2010 11:38 To: oic@lists.oasis-open.org Subject: [oic] Version Control Commit by bart.hanssens Author: bart.hanssens Date: 2010-06-14 14:37:32 -0400 (Mon, 14 Jun 2010) New Revision: 150 Web View: http://tools.oasis-open.org/version-control/browse/wsvn/oic/?rev=150&sc=1 Modified: Advisories/00001/oic-interop-adv-00001.html Log: moving references section to start of document --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]