Dear Scot, dear Docutils developers, On 2017-09-04, Scott Kostyshak wrote:
>> The problem is, however, that users upgrading from 2.2 have read the >> 2.2.0 RELEASE NOTES already and won't see the need to re-read them, > Agreed. >> thus missing the information. Nevertheless, they are still affected by >> the changes when opening pre-2.2 documents (and will forever, as we >> voted not to revert the decision to merge literal and ligature dashes >> in the LyX source). > You are thinking maybe of a user who created their document with 2.1.x, > edited it briefly in 2.2.x but not enough to realize a change/problem, > and now are upgrading to 2.3.0 and will be reading the release notes? I am looking for the right place of a warning to all users of LyX 2.2 and newer, as they may see problems with dashes in documents created with version up to 2.1. > I think we can address it with e.g. a concise "if you created the first > version of your document in LyX pre-2.2, your dashes may have been > changed. For more information, please see..." I think that makes more > sense that putting a lot of details about this issue in the 2.3.0 > release notes. I think that the important thing is to let the user know > the conditions under which they might experience a caveat. > I don't really have a strong opinion on this, but I think a concise > description of the conditions for a caveat, combined with a reference > for further information, could be a reasonable compromise. Agreed. I will prepare a patch for review. Günter
