Pavel Sanda wrote:
> at least we could add empty file format bump to have free slot in case
> something undesirable appears during 2.0.x...
An empty file format change does not work well. As soon as somebody opened
the file with 2.0 and saved it, the file format change is useless for that
docum
Georg Baum wrote:
> Georg Baum wrote:
>
> > If you want a file format change the only sensible solution is to add code
> > in lyx2lyx that creates preamble code that overwrites the new translation,
> > so that the output is still identical with the one produced by the old
> > version. Warning mess
Georg Baum wrote:
> If you want a file format change the only sensible solution is to add code
> in lyx2lyx that creates preamble code that overwrites the new translation,
> so that the output is still identical with the one produced by the old
> version. Warning messages are useless IMHO: It is e
Pavel Sanda wrote:
> Georg Baum wrote:
>> >> exported documents.
>> >> To update the translations from the .po files, run
>> >> make ../lib/layouttranslations
>> >> from po.
>> >
>> > shall we bump file version number in case somewthing goes wrong?
>>
>> How would that help? If we really get a d
José Matos wrote:
> In order to complete my other message. Note that with the changes in the
> latex
> packages that the document uses it is possible that the final document output
> is different even if we generate the same tex output.
its true that when some babel package changes underneath w
On 30-3-2011 13:33, José Matos wrote:
On Wednesday 30 March 2011 11:45:59 Pavel Sanda wrote:
its not strictly related to the format bumps (we changed the output, not
fileformat itself) however i still contemplate whether we should warn user
somehow, that his particular document will have differe
On Wednesday 30 March 2011 11:45:59 Pavel Sanda wrote:
> its not strictly related to the format bumps (we changed the output, not
> fileformat itself) however i still contemplate whether we should warn user
> somehow, that his particular document will have different output than
> before
>
> it
On Wednesday 30 March 2011 11:45:59 Pavel Sanda wrote:
> its not strictly related to the format bumps (we changed the output, not
> fileformat itself) however i still contemplate whether we should warn user
> somehow, that his particular document will have different output than
> before
>
> it
it could be nightmare that you grab years old lyx article, typeset it and the
output will be different on few places, which can be easily overseen.
it can even change paging due to the different string lengths.
what do others think?
pavel
What about writing these translated strings into the
Georg Baum wrote:
> >> exported documents.
> >> To update the translations from the .po files, run
> >> make ../lib/layouttranslations
> >> from po.
> >
> > shall we bump file version number in case somewthing goes wrong?
>
> How would that help? If we really get a different translation than befo
Georg Baum wrote:
> would be a normal bug IMO. Apart form that I am pretty sure that it does not
> go wrong ;-)
ok.p
Pavel Sanda wrote:
> b...@lyx.org wrote:
>>
>> First version of separate translation machinery for strings that go into
>> exported documents.
>> To update the translations from the .po files, run
>> make ../lib/layouttranslations
>> from po.
>
> shall we bump file version number in case somewth
b...@lyx.org wrote:
> Author: baum
> Date: Wed Mar 23 20:17:15 2011
> New Revision: 38016
> URL: http://www.lyx.org/trac/changeset/38016
>
> Log:
> First version of separate translation machinery for strings that go into
> exported documents.
> To update the translations from the .po files, run
>
13 matches
Mail list logo
