On Sun, Oct 6, 2013 at 7:12 AM, Martin Hoffmann wrote:
> On 06.10.2013 10:25, Jürgen Spitzmüller wrote:
>> Scott Kostyshak wrote:
>>> Welcome to the list!
>>
>> Yes, welcome on board, Martin!
>>
>>> I tested your patch and it works well for me. Does anyone else know
>>> whether this is a correct f
Richard Heck wrote:
> The things that are turning up in the corrupt file look to me like UI
> strings. So I'm guessing that what happens is that, while the file is
> being exported, we are calling the iconv stuff to deal with UI strings,
> and we end up with a mess. Perhaps this is more likely to
On Mon, Oct 07, 2013 at 09:18:38PM +0200, Vincent van Ravesteijn wrote:
> When I open the document in a plain text editor, it complains about
> characters that cannot be represented in the current codeset (or
> something like that).
Maybe your editor is not configured for reading utf8 encoded tex
Enrico Forestieri wrote:
> On Mon, Oct 07, 2013 at 11:39:57AM -0700, Pavel Sanda wrote:
>
>> Enrico Forestieri wrote:
>> > The problem here is that to_utf8() (and most probably all other
>> > conversion routines) is not thread safe, maybe due to the static
>> > output buffer in iconv_convert().
>
Richard Heck wrote:
> Great work, Enrico. I've posted the patch to the bug report. We'll see
> what the reporter has to say.
Great work indeed!
> It is very strange that I can't reproduce, if this is the cause, and,
> indeed, that people haven't been seeing this bug all along.
This is not stran
Am 15.09.2013 17:04, schrieb Jürgen Spitzmüller:
Am Sonntag 15 September 2013, 16:43:49 schrieb Jean-Pierre Chrétien:
Typos corrected in the attached patches both for branch and master versions
of Intro.lyx.
I also corrected the link to www.lyx.org/Translation to point towards the
French vers
On 10/07/2013 04:16 PM, Vincent van Ravesteijn wrote:
Op 7-10-2013 21:18, Vincent van Ravesteijn schreef:
Op 7-10-2013 21:05, Enrico Forestieri schreef:
On Mon, Oct 07, 2013 at 02:28:18PM -0400, Richard Heck wrote:
It is very strange that I can't reproduce, if this is the cause,
and, indeed, t
On Mon, Oct 7, 2013 at 4:16 PM, Vincent van Ravesteijn wrote:
> Op 7-10-2013 21:18, Vincent van Ravesteijn schreef:
> Something else I notice: Sometime the macros are exported as "\newcommand"
> and sometimes as "\renewcommand". This seems to be rather random.
>
I saw this too. For me the differe
Op 7-10-2013 21:18, Vincent van Ravesteijn schreef:
Op 7-10-2013 21:05, Enrico Forestieri schreef:
On Mon, Oct 07, 2013 at 02:28:18PM -0400, Richard Heck wrote:
It is very strange that I can't reproduce, if this is the cause,
and, indeed, that people haven't been seeing this bug all along.
Act
Op 7-10-2013 21:05, Enrico Forestieri schreef:
So, the bug also depends on the structure of the document, somehow.
Is the registered trademark symbol on line 460 and 480 of the lyx file
the problem maybe ?
Vincent
Op 7-10-2013 21:05, Enrico Forestieri schreef:
On Mon, Oct 07, 2013 at 02:28:18PM -0400, Richard Heck wrote:
It is very strange that I can't reproduce, if this is the cause,
and, indeed, that people haven't been seeing this bug all along.
Actually, all my files are converted correctly. But usin
On Mon, Oct 07, 2013 at 02:28:18PM -0400, Richard Heck wrote:
>
> It is very strange that I can't reproduce, if this is the cause,
> and, indeed, that people haven't been seeing this bug all along.
Actually, all my files are converted correctly. But using the one
attached to the bug report trigge
On Mon, Oct 07, 2013 at 11:39:57AM -0700, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > The problem here is that to_utf8() (and most probably all other
> > conversion routines) is not thread safe, maybe due to the static
> > output buffer in iconv_convert().
>
> Huh, iconv strikes back. We al
Enrico Forestieri wrote:
> The problem here is that to_utf8() (and most probably all other
> conversion routines) is not thread safe, maybe due to the static
> output buffer in iconv_convert().
Huh, iconv strikes back. We already knew that iconv is not thread safe
and I remember we already mutexed
On 10/07/2013 02:10 PM, Enrico Forestieri wrote:
On Sun, Oct 06, 2013 at 12:09:50PM -0400, Richard Heck wrote:
I just wanted to call everyone's attention to this bug:
http://www.lyx.org/trac/ticket/8854
It appears to be a very nasty dataloss bug in 2.1-beta1. What seems
to be happening is that,
On Mon, Oct 07, 2013 at 08:10:33PM +0200, Enrico Forestieri wrote:
>
> The problem here is that to_utf8() (and most probably all other
> conversion routines) is not thread safe, maybe due to the static
> output buffer in iconv_convert().
Yes, this seems to be the case. The attached alternative pa
On Sun, Oct 06, 2013 at 12:09:50PM -0400, Richard Heck wrote:
>
> I just wanted to call everyone's attention to this bug:
> http://www.lyx.org/trac/ticket/8854
> It appears to be a very nasty dataloss bug in 2.1-beta1. What seems
> to be happening is that, on save, the LyX file is corrupted in ver
Op 6-10-2013 18:09, Richard Heck schreef:
I just wanted to call everyone's attention to this bug:
http://www.lyx.org/trac/ticket/8854
It appears to be a very nasty dataloss bug in 2.1-beta1. What seems to
be happening is that, on save, the LyX file is corrupted in very weird
ways, with random
I tried to export user guide under valgrind, but got no interesting warnibg.
JMarc
Richard Heck a écrit :
>On 10/06/2013 01:38 PM, Jean-Marc Lasgouttes wrote:
>> Le 06/10/2013 18:09, Richard Heck a écrit :
>>>
>>> I just wanted to call everyone's attention to this bug:
>>> http://www.lyx.org/tr
Scott Kostyshak wrote:
> I'm unsure also. It would be nice though to have a policy though.
> Perhaps we could put it in ./lib/doc/Development.lyx.
Yep. It would be even nicer if we could have ct markup from git revisions. If
we track manually, we eventually will have to merge (pretty soon now, I
On 10/06/2013 01:38 PM, Jean-Marc Lasgouttes wrote:
Le 06/10/2013 18:09, Richard Heck a écrit :
I just wanted to call everyone's attention to this bug:
http://www.lyx.org/trac/ticket/8854
It appears to be a very nasty dataloss bug in 2.1-beta1. What seems to
be happening is that, on save, the L
On Mon, Oct 7, 2013 at 11:12 AM, Jürgen Spitzmüller wrote:
> Scott Kostyshak wrote:
>> I thought that for documentation we use change-tracking so that we can
>> see which parts need to be translated. Is the point that nothing needs
>> to be translated here? Or that it's too late to send to transla
Scott Kostyshak wrote:
> I thought that for documentation we use change-tracking so that we can
> see which parts need to be translated. Is the point that nothing needs
> to be translated here? Or that it's too late to send to translators
> for 2.1 ?
I didn't use it because there was no change tra
On Mon, Oct 7, 2013 at 9:26 AM, Juergen Spitzmueller wrote:
> commit c5c9e26feeccbb90e2b2f24d931e02820d6b9cad
> Author: Juergen Spitzmueller
> Date: Mon Oct 7 15:26:45 2013 +0200
>
> Clarify instructions on how to set up the thesaurus (#8811)
>
I thought that for documentation we use chang
24 matches
Mail list logo
