1.6.5
--
Andrés
Enrico Forestieri writes:
> Maybe a new flag AS_STR_TOC should be introduced for Paragraph::asString,
> in order to discriminate between tocString and a new clipboardString (or
> somesuch) method. Of course, all uses of asString should be audited.
Or maybe a flag like AS_COMPACT_INSETS that we co
On Thursday 08 October 2009 Pavel Sanda wrote:
> hi,
>
> i have small question for people using lyx + subversion. i'm thinking about
> using some svn syntax from version >=1.5 for new lyx commands. how big is
> the crowd of people still using svn 1.4 or in other words could you drop
> me version
On Thu October 8 2009 17:50:26 Pavel Sanda wrote:
> hi,
>
> i have small question for people using lyx + subversion. i'm thinking about
> using some svn syntax from version >=1.5 for new lyx commands. how big is
> the crowd of people still using svn 1.4 or in other words could you drop
> me vers
On Fri, Oct 09, 2009 at 11:38:10AM +0200, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > I'll leave to others the decision about renaming tocString as textString
> > (which is the most obvious and easy thing to do, IMHO).
>
> I still think it should not be renamed, but splitted up to two
Hi Pavel
I am still using svn 1.4.6.
That's what came with Ubuntu 8.04 (hardy heron) which I am still using.
But I am only a tester anyway, so count me only half ;)
- Sebastian
Enrico Forestieri wrote:
> I'll leave to others the decision about renaming tocString as textString
> (which is the most obvious and easy thing to do, IMHO).
I still think it should not be renamed, but splitted up to two functions. We
should not use the same function for pasting and the toc.
Jür
On Sat, Oct 03, 2009 at 11:56:50AM +0200, Jürgen Spitzmüller wrote:
> Is it really correct to assume utf8 in plaintext (after all, other plaintext
> methods use the runparams' encoding, so we would get a mish-mash of encodings,
> wouldn't we)? I agree that utf8 is te correct encoding for pasting a
