Community
Participate
Working Groups
I20100928-1200. New option to not use capped algorithm misses documentation.
Tomasz, I think Krzysztof could handle that.
I think we should consider backporting an eventual fix to 3.6.2 as well, shouldn't we?
(In reply to comment #2) > I think we should consider backporting an eventual fix to 3.6.2 as well, > shouldn't we? We should.
Created attachment 180309 [details] patch Here is text patch.
Created attachment 180313 [details] Image219_pref_cv.png Here is Image219_pref_cv.png which should be copied into images folder in org.eclipse.platform.doc.user.
Created attachment 180314 [details] Image219_pref_cv2.png Here is Image219_pref_cv2.png which should be copied into images folder in org.eclipse.platform.doc.user.
Created attachment 180316 [details] "Text Compare" tab in classic theme
Created attachment 180317 [details] mylyn/context/zip
Created attachment 180318 [details] more precise description
Dani, is the description clear enough in your opinion? "The capping mechanism is used to speed up finding differences in large files. In that case, the result may be inaccurate and contain too many changes. Turn this option on, if you prefer a precise result in favour of possibly longer calculation time."
(In reply to comment #10) > Dani, is the description clear enough in your opinion? > > "The capping mechanism is used to speed up finding differences in large files. > In that case, the result may be inaccurate and contain too many changes. Turn > this option on, if you prefer a precise result in favour of possibly longer > calculation time." AFAIK "inaccurate and contain many changes" is wrong: it finds all changes but the displayed region that covers them might be bigger than needed.
(In reply to comment #11) > AFAIK "inaccurate and contain many changes" is wrong: it finds all changes but > the displayed region that covers them might be bigger than needed. Right, what about: "The capping mechanism is used to speed up finding differences in large files. In case where the capping happens the result can either be correct or it can contain too many changes, but it never misses any change. Turn this option on, if you prefer a precise result in favour of possibly longer calculation time." ?
Looks good. Minor change: >either be correct or it can contain too many changes, either be correct or it can display too many changes,
Done, thanks Dani. The doc has been updated in HEAD. Filed bug 327425 for backporting the same fix to 3.6.x branch.
Verified in I20101025-1800.