Jean-Marc Lasgouttes wrote:
> > I wouldn't mind to twist our definition of "ASCII" to mean "UTF-8".
>
> We could have a pref that is the encoding we use for text import/export
> and maybe for clipboard (is encoding always known in this case?)
Good idea. For text input, we should additionally add a
Vincent van Ravesteijn wrote:
> Any opinions on whether this is enough to close the bug ? The fact that
> the input completion leads to an assertion might have to be fixed too.
I think so, too. Stefan should have a look.
> http://bugzilla.lyx.org/show_bug.cgi?id=5731
>
> I assume I can apply this
Vincent van Ravesteijn schrieb:
The patch will be huge and I need to be very careful.
OK then better not before LyX 1.6.3. I'll test it as best as possible in the meantime because I have
to use change tracking quite often these days.
I will do it shortly, but I'm fixing some critical bugs
Uwe Stöhr schreef:
Vincent van Ravesteijn schrieb:
Otherwise I ask for an OK or comments for this patch.
Hello Vincent, what about your patch? When I remember correctly we
agreed to put it in for LyX 1.6.x and it was also requested in
bugzilla. Can you put it to trunk please?
Jürgen, am I
Vincent van Ravesteijn schrieb:
Otherwise I ask for an OK or comments for this patch.
Hello Vincent, what about your patch? When I remember correctly we agreed to put it in for LyX 1.6.x
and it was also requested in bugzilla. Can you put it to trunk please?
Jürgen, am I right? If so this sh
Jean-Marc Lasgouttes schreef:
Le 2 févr. 09 à 22:44, v...@lyx.org a écrit :
Author: vfr
Date: Mon Feb 2 22:44:37 2009
New Revision: 28326
URL: http://www.lyx.org/trac/changeset/28326
Log:
Fix bug 5731. http://bugzilla.lyx.org/show_bug.cgi?id=5731
Insert column after the current one, then copy
Le 2 févr. 09 à 22:44, v...@lyx.org a écrit :
Author: vfr
Date: Mon Feb 2 22:44:37 2009
New Revision: 28326
URL: http://www.lyx.org/trac/changeset/28326
Log:
Fix bug 5731. http://bugzilla.lyx.org/show_bug.cgi?id=5731
Insert column after the current one, then copy the current one to
the new on
v...@lyx.org schreef:
Author: vfr
Date: Mon Feb 2 22:44:37 2009
New Revision: 28326
URL: http://www.lyx.org/trac/changeset/28326
Log:
Fix bug 5731. http://bugzilla.lyx.org/show_bug.cgi?id=5731\nInsert column after
the current one, then copy the current one to the new one
Modified:
lyx-dev
I wouldn't mind to twist our definition of "ASCII" to mean "UTF-8".
We could have a pref that is the encoding we use for text import/export
and maybe for clipboard (is encoding always known in this case?)
JMarc
On Mon, Feb 02, 2009 at 04:19:04PM +0100, Helge Hafting wrote:
> Jürgen Spitzmüller wrote:
>> Les Denham wrote:
>> > Is there a way of making the quotes strictly ASCII? I'm getting into
>> > trouble with a mailing list which insists on plain ASCII text.
>>
>> Not without hacking the source, I'm
Uwe Stöhr wrote:
For the new phantom inset, the paragraph dialog must not be called by
the user, because paragraph settings would lead to LaTeX errors. This
is the same as with the ERT and the Index inset.
I have now this code in stdinsets.inc:
InsetLayout Phantom:Phantom
LatexType
Jürgen Spitzmüller wrote:
Les Denham wrote:
> Is there a way of making the quotes strictly ASCII? I'm getting into
> trouble with a mailing list which insists on plain ASCII text.
Not without hacking the source, I'm afraid.
Question to lyx-devel: is "plain text" supposed to produce ASCII? If
Vincent van Ravesteijn - TNW wrote:
> This sounds like all files with a numbered equation lead to a crash. But
> this bug was only about 'invalid' files which had both a \nonumber and a
> \label specified. Wasn't it ?
Feel free to improve the description.
> Do you know why the crash occurred when
> +- Fix crash when reading document with a numbered equation (bug
5688).
> +
> - Fix conversion of documents that have index insets following an
index
> list inset to LyX 1.6's format (bug 5713).
> Affected files that have already been mis-converted can be repaired
by
This sounds like a
Jean-Marc Lasgouttes wrote:
> Is it me, or could this sentence use a full stop somewhere in the
> middle?
It could. You see, I was lazy when copying from your bugzilla comment.
Jürgen
sp...@lyx.org writes:
> + // The buffer is set at the end of readInset
> + // when parsing the inset, buffer_ is 0.
> + return;
Is it me, or could this sentence use a full stop somewhere in the
middle?
JMarc
Vincent van Ravesteijn - TNW wrote:
> I think this must be solved before releasing 1.6.2.
Any input is highly appreciated. There is some ongoing discussion about the
correct approach between Jean-Marc and myself. I have posted a tentative patch
that will probably solve all these issues (but is o
Jürgen Spitzmüller wrote:
> > attached tested patch for branch.
>
> 1.6.3 perhaps? We already have many features and still have many unresolved
> bugs for 1.6.2.
ok, i will wait
pavel
> > > D:\LyX\lyx-1.6.1\src\CoordCache.cpp(39): break on pointer: 02B6A408
> > > hint: x size: 8
> > > D:\LyX\lyx-1.6.1\src\support\lassert.cpp(21): ASSERTION false
> > > VIOLATED IN D:\LyX\lyx-1.6.1\src\CoordCache.cpp:40
> > > Completed
> > >
> > Could you please elaborate on when this cras
Jürgen Spitzmüller writes:
> IIRC this is only the case if you do not use proper single quotation marks
> (via Alt-" with cua). So I would qualify this as a user error, not as a bug.
Thank you kindly for the tip. User error has been rectified.
Cheers, Sam
Pavel Sanda wrote:
> > this is really cool feature and i will cry for having this in branch too,
> > Juergen :)
>
> attached tested patch for branch.
1.6.3 perhaps? We already have many features and still have many unresolved
bugs for 1.6.2.
Jürgen
21 matches
Mail list logo
