On 05/04/2011 3:49 PM, Georg Baum wrote:
Richard Heck wrote:
I meant not to be proposing it for 2.0.0, precisely for the reason you
mention, but I think it would be OK for a later release in the 2.0.x
series. Of course, that is up to Pavel: whether he'll accept a patch
that adds a BufferParam to control this as yet non-existent feature.
(It's been done before.)
I vote against that. What happens if a user loads a file created by 2.0.1
(with activated local prettyref translations) with 2.0.0? 2.0.0 could either
refuse to load such files (bad), or it could load them, but produce
different output (bad as well, since the file format bump should avoid
exactly that).
Please don't get me wrong: I agree completely about the usefulness of local
refstyle translations, but IMO they are not a must-have for the 2.0.x
series. Prettyref translations have been broken forever. You improved the
situation for some languages with your refstyle support, so 2.0 already has
an advantage already. It would be nice to have more, but at some point in
time it must be decided that a release is finished, and this will always
include some bugs that are still open.
Georg
+1
no showstopper here
refstyle supprt already adds a nice feature and makes compilable
documents :)
--
Julien
