Re: Plain text output

2007-02-27 Thread Georg Baum
Am Sonntag, 25. Februar 2007 18:53 schrieb Abdelrazak Younes: > 3203 maj possible to import non-utf8 text files > I'd say non-blocker; Georg? I have no idea. I personally don't have a problem if only utf8 text can be imported, but I suspect that users will see that differently, especially sinc

Re: Plain text output

2007-02-26 Thread Abdelrazak Younes
Jean-Marc Lasgouttes wrote: "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> "Blocker" is a function of the nature of the bug. A "Blocker" Lars> bug is a bug that makes LyX completely unusable. Lars> "pri 1" is more political. And we can f.ex. decide that all "pri Lars> 1" bugs

Re: Plain text output

2007-02-26 Thread Abdelrazak Younes
Lars Gullik Bjønnes wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: | > | >> We need to prioritize the bugs, I agree. | > | > I propose that we promote some of the "major" bugs to "blocker". | > | > Then only the critical (if possible) and blocker will have to be | > | > fixed for 1.5.0. T

Re: Plain text output

2007-02-26 Thread Jean-Marc Lasgouttes
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> "Blocker" is a function of the nature of the bug. A "Blocker" Lars> bug is a bug that makes LyX completely unusable. Lars> "pri 1" is more political. And we can f.ex. decide that all "pri Lars> 1" bugs _must_ be fixed before fi

Re: Plain text output

2007-02-26 Thread Lars Gullik Bjønnes
Abdelrazak Younes <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes wrote: | > Abdelrazak Younes <[EMAIL PROTECTED]> writes: | > | Abdelrazak Younes wrote: | > | > José Matos wrote: | > | >> On Saturday 24 February 2007 4:24:41 pm Michael Gerz wrote: | > | >>> Ah, and then there are 527 bugs left

Re: Plain text output

2007-02-26 Thread Abdelrazak Younes
Lars Gullik Bjønnes wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: | Abdelrazak Younes wrote: | > José Matos wrote: | >> On Saturday 24 February 2007 4:24:41 pm Michael Gerz wrote: | >>> Ah, and then there are 527 bugs left (an all-time high?): | >>> http://tinyurl.com/y7hdzc | > Only 82 o

Re: Plain text output

2007-02-26 Thread Jean-Marc Lasgouttes
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> Jean-Marc Lasgouttes wrote: >>> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: >> Abdelrazak> 3204 maj file insertion cannot be undone -> blocker? >> Fix below. Committing now. Abdelrazak> Good guy

Re: Plain text output

2007-02-26 Thread Abdelrazak Younes
Jean-Marc Lasgouttes wrote: "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> 3204 maj file insertion cannot be undone -> blocker? Fix below. Committing now. Good guy :-) Abdel.

Re: Plain text output

2007-02-25 Thread Lars Gullik Bjønnes
Abdelrazak Younes <[EMAIL PROTECTED]> writes: | Abdelrazak Younes wrote: | > José Matos wrote: | >> On Saturday 24 February 2007 4:24:41 pm Michael Gerz wrote: | >>> Ah, and then there are 527 bugs left (an all-time high?): | >>> http://tinyurl.com/y7hdzc | > Only 82 of which are genuine to 1.5.0s

Re: Plain text output

2007-02-25 Thread Lars Gullik Bjønnes
[EMAIL PROTECTED] writes: | On Sun, 25 Feb 2007, Lars Gullik Bjønnes wrote: | | > | Instead of bugzilla + pmwiki + html-www (+ www-devel). | > | > I not sure it is _that_ nice. | > | > But for repository tasks I might agree. (even if mediawiki is a much | > nicer wiki...) | | Out of curiosity, w

Re: Plain text output

2007-02-25 Thread Jean-Marc Lasgouttes
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> 3204 maj file insertion cannot be undone -> blocker? Fix below. Committing now. JMarc Index: src/lyx_cb.C === --- src/lyx_cb.C (révision 17343) +++ src

Re: Plain text output

2007-02-25 Thread christian . ridderstrom
On Sun, 25 Feb 2007, Michael Gerz wrote: Lars Gullik Bjønnes schrieb: | Instead of bugzilla + pmwiki + html-www (+ www-devel). I not sure it is _that_ nice. But for repository tasks I might agree. (even if mediawiki is a much nicer wiki...) The benefit of Trac is that everything is tight

Re: Plain text output

2007-02-25 Thread christian . ridderstrom
On Sun, 25 Feb 2007, Lars Gullik Bjønnes wrote: | Instead of bugzilla + pmwiki + html-www (+ www-devel). I not sure it is _that_ nice. But for repository tasks I might agree. (even if mediawiki is a much nicer wiki...) Out of curiosity, what is it about mediawiki that you like? Is it the

Re: Plain text output

2007-02-25 Thread Abdelrazak Younes
Abdelrazak Younes wrote: José Matos wrote: On Saturday 24 February 2007 4:24:41 pm Michael Gerz wrote: Ah, and then there are 527 bugs left (an all-time high?): http://tinyurl.com/y7hdzc Only 82 of which are genuine to 1.5.0svn. I propose that we concentrate on those. We need to priori

Re: Plain text output

2007-02-25 Thread Abdelrazak Younes
José Matos wrote: On Saturday 24 February 2007 4:24:41 pm Michael Gerz wrote: Ah, and then there are 527 bugs left (an all-time high?): http://tinyurl.com/y7hdzc Only 82 of which are genuine to 1.5.0svn. I propose that we concentrate on those. We need to prioritize the bugs, I agree.

Re: Plain text output

2007-02-25 Thread Michael Gerz
Lars Gullik Bjønnes schrieb: | Instead of bugzilla + pmwiki + html-www (+ www-devel). I not sure it is _that_ nice. But for repository tasks I might agree. (even if mediawiki is a much nicer wiki...) The benefit of Trac is that everything is tightly integrated. I don't see why this is not t

Re: Plain text output

2007-02-25 Thread Lars Gullik Bjønnes
Michael Gerz <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes schrieb: | > Michael Gerz <[EMAIL PROTECTED]> writes: | > | > | José Matos schrieb: | > | > On Sunday 25 February 2007 8:39:31 am Michael Gerz wrote: | > | > | > | >> I still can't see the announcement on our web site. | > | >> | > | >

Re: Plain text output

2007-02-25 Thread Michael Gerz
Lars Gullik Bjønnes schrieb: Michael Gerz <[EMAIL PROTECTED]> writes: | José Matos schrieb: | > On Sunday 25 February 2007 8:39:31 am Michael Gerz wrote: | > | >> I still can't see the announcement on our web site. | >> | > | > But you can now. :-) | > | > BTW IMHO without RSS a web announcement

Re: Plain text output

2007-02-25 Thread Lars Gullik Bjønnes
Michael Gerz <[EMAIL PROTECTED]> writes: | José Matos schrieb: | > On Sunday 25 February 2007 8:39:31 am Michael Gerz wrote: | > | >> I still can't see the announcement on our web site. | >> | > | > But you can now. :-) | > | > BTW IMHO without RSS a web announcement is so 90's ;-) , it would be |

Re: Plain text output

2007-02-25 Thread Martin Vermeer
On Sat, 24 Feb 2007, Michael Gerz wrote: José, all, of things are still subject to optimization (e.g., correct line indentation, label translation based on par language etc.) but plain text output has become good enough for my purposes (= grammar checking with MS Word) and line breaking h

Re: Plain text output

2007-02-25 Thread Michael Gerz
José Matos schrieb: On Sunday 25 February 2007 8:39:31 am Michael Gerz wrote: I still can't see the announcement on our web site. But you can now. :-) BTW IMHO without RSS a web announcement is so 90's ;-) , it would be nice if we could support RSS in the page. I said it multiple

Re: Plain text output

2007-02-25 Thread José Matos
On Sunday 25 February 2007 8:39:31 am Michael Gerz wrote: > Great! I hope you are actually using it :-) In case it was not clear I am using it. :-) > Michael -- José Abílio

Re: Plain text output

2007-02-25 Thread José Matos
On Sunday 25 February 2007 8:39:31 am Michael Gerz wrote: > I still can't see the announcement on our web site. But you can now. :-) BTW IMHO without RSS a web announcement is so 90's ;-) , it would be nice if we could support RSS in the page. -- José Abílio

Re: Plain text output

2007-02-25 Thread Michael Gerz
José Matos schrieb: Since the first beta has not been announced yet, I guess there is no need to hurry. Expect something by the end of the week. This sentence I don't grok... :-) At the time you sent this sentence 1.5.0beta1 had been announced. I still can't see the announcement

Re: Plain text output

2007-02-24 Thread José Matos
On Saturday 24 February 2007 4:24:41 pm Michael Gerz wrote: > José, all, > > I just wanted to tell you that I completed my work on plain text output. > Unless I find a new bug, I won't touch this part of the code anymore. Of > course, a lot of things are still subject to optimization (e.g., correct

Re: Plain text output

2007-02-24 Thread Michael Gerz
Georg Baum schrieb: Am Samstag, 24. Februar 2007 17:24 schrieb Michael Gerz: I think we have to fix at least the most critical and most annoying ones for 1.5.0 final. For instance, my productivity is really weakened by #2843. This one is fixed. Which one did you mean? Oops... 24

Re: Plain text output

2007-02-24 Thread Georg Baum
Am Samstag, 24. Februar 2007 17:24 schrieb Michael Gerz: > I think we have to fix at least the most critical and most annoying ones > for 1.5.0 final. For instance, my productivity is really weakened by > #2843. This one is fixed. Which one did you mean? Georg

Re: plain text output - how to proceed

2006-09-10 Thread Georg Baum
Am Sonntag, 10. September 2006 10:40 schrieb Peter Kümmel: > But there are warnings when compiling with msvc: > > stream6.cpp(252) : warning C4244: 'return' : conversion from 'ascii_ctype_facet::char_type' to 'char', possible loss of data > stream6.cpp(253) : warning C4244: 'argument' : conversio

Re: plain text output - how to proceed

2006-09-10 Thread Peter Kümmel
Your code is correct! It were my wrong editor settings, after enabling autodetection of UTF8 it looks correct, see png. But there are warnings when compiling with msvc: stream6.cpp(252) : warning C4244: 'return' : conversion from 'ascii_ctype_facet::char_type' to 'char', possible loss of data s

Re: plain text output - how to proceed

2006-09-09 Thread Enrico Forestieri
On Sat, Sep 09, 2006 at 05:50:42PM +0200, Georg Baum wrote: > I believe that this version should work on any OS. I can confirm that with mingw and cygwin the same output as your is generated. -- Enrico

Re: plain text output - how to proceed

2006-09-09 Thread Peter Kümmel
Georg Baum wrote: > Am Dienstag, 5. September 2006 14:35 schrieb Abdelrazak Younes: >> Peter Kümmel wrote: >>> In my ordinary text editor (ultraedit) it doen't loock like a text > file. >> Same for me in wordpad... attached the file. > > Can you please try this updated test program? The screen ou

Re: plain text output - how to proceed

2006-09-09 Thread Georg Baum
Am Dienstag, 5. September 2006 14:35 schrieb Abdelrazak Younes: > Peter Kümmel wrote: > > In my ordinary text editor (ultraedit) it doen't loock like a text file. > > Same for me in wordpad... attached the file. Can you please try this updated test program? The screen output should look like in

Re: plain text output - how to proceed

2006-09-05 Thread Enrico Forestieri
On Tue, Sep 05, 2006 at 02:09:25PM +0200, Georg Baum wrote: > Enrico Forestieri wrote: > > > Georg, I tried your test program on cygwin and, after adding an > > "#include " line, it fails to compile as follows: > > > > $ g++ stream2.cpp -o stream2 > > stream2.cpp: In function `int main()': > > s

Re: plain text output - how to proceed

2006-09-05 Thread Enrico Forestieri
On Tue, Sep 05, 2006 at 02:26:55PM +0200, Peter Kümmel wrote: > Georg Baum wrote: [...] > > std::wcerr should be declared in iostream. If gcc on cygwin does not have it > > then it is not standard conforming. Possibly. The wide stream versions are #ifdef'd out in iostream: #ifdef _GLIBCXX_USE_WC

Re: plain text output - how to proceed

2006-09-05 Thread Abdelrazak Younes
Peter Kümmel wrote: Georg Baum wrote: Abdelrazak Younes wrote: Ah... with this change I have then the same output as yours: test: abcd 228246252 20 e4 f6 fc 196214220 20 c4 d6 dc abcd That looks good, but the generated file is more interesting. Does it contain abcd äöü äöü abcd

Re: plain text output - how to proceed

2006-09-05 Thread Peter Kümmel
Georg Baum wrote: > Enrico Forestieri wrote: > >> Georg, I tried your test program on cygwin and, after adding an >> "#include " line, it fails to compile as follows: >> >> $ g++ stream2.cpp -o stream2 >> stream2.cpp: In function `int main()': >> stream2.cpp:230: error: `wcerr' is not a member of

Re: plain text output - how to proceed

2006-09-05 Thread Georg Baum
Enrico Forestieri wrote: > Georg, I tried your test program on cygwin and, after adding an > "#include " line, it fails to compile as follows: > > $ g++ stream2.cpp -o stream2 > stream2.cpp: In function `int main()': > stream2.cpp:230: error: `wcerr' is not a member of `std' > stream2.cpp:238: er

Re: plain text output - how to proceed

2006-09-05 Thread Enrico Forestieri
On Mon, Sep 04, 2006 at 10:46:43PM +0200, Georg Baum wrote: > Peter and Abdel, can you please test whether the attached test program > works (or could be made to work) on windows with lyx::char_type == > boost::uint32_t? > > If yes, then I'd like to put the attached patch in and proceed with >

Re: plain text output - how to proceed

2006-09-05 Thread Georg Baum
Peter Kümmel wrote: > In my ordinary text editor (ultraedit) it doen't loock like a text file. > Also firefox only shows numbers. Both should recognize utf8 text files. >> encoded in utf8? > How do I check? Please send it (in a .zip archive so that it does not get altered), I'll have a look.

Re: plain text output - how to proceed

2006-09-05 Thread Lars Gullik Bjønnes
Peter Kümmel <[EMAIL PROTECTED]> writes: | Georg Baum wrote: | > Abdelrazak Younes wrote: | > | >> Ah... with this change I have then the same output as yours: | >> | >> test: | >> abcd | >> 228246252 | >> 20 e4 f6 fc | >> 196214220 | >> 20 c4 d6 dc | >> abcd | > | > That looks good, but

Re: plain text output - how to proceed

2006-09-05 Thread Peter Kümmel
Georg Baum wrote: > Abdelrazak Younes wrote: > >> Ah... with this change I have then the same output as yours: >> >> test: >> abcd >> 228246252 >> 20 e4 f6 fc >> 196214220 >> 20 c4 d6 dc >> abcd > > That looks good, but the generated file is more interesting. Does it contain > > abcd >

Re: plain text output - how to proceed

2006-09-05 Thread Georg Baum
Georg Baum wrote: > Abdelrazak Younes wrote: > >> Ah... with this change I have then the same output as yours: >> >> test: >> abcd >> 228246252 >> 20 e4 f6 fc >> 196214220 >> 20 c4 d6 dc >> abcd > > That looks good, but the generated file is more interesting. Does it > contain > > abc

Re: plain text output - how to proceed

2006-09-05 Thread Georg Baum
Abdelrazak Younes wrote: > Ah... with this change I have then the same output as yours: > > test: > abcd > 228246252 > 20 e4 f6 fc > 196214220 > 20 c4 d6 dc > abcd That looks good, but the generated file is more interesting. Does it contain abcd äöü äöü abcd encoded in utf8? Geor

Re: plain text output - how to proceed

2006-09-05 Thread Abdelrazak Younes
Peter Kümmel wrote: Abdelrazak Younes wrote: Georg Baum wrote: Peter and Abdel, can you please test whether the attached test program works (or could be made to work) on windows with lyx::char_type == boost::uint32_t? If yes, then I'd like to put the attached patch in and proceed with solution

Re: plain text output - how to proceed

2006-09-05 Thread Peter Kümmel
Abdelrazak Younes wrote: > Georg Baum wrote: >> Peter and Abdel, can you please test whether the attached test program >> works (or could be made to work) on windows with lyx::char_type == >> boost::uint32_t? >> >> If yes, then I'd like to put the attached patch in and proceed with >> solution 2) a

Re: plain text output - how to proceed

2006-09-05 Thread Abdelrazak Younes
Georg Baum wrote: Peter and Abdel, can you please test whether the attached test program works (or could be made to work) on windows with lyx::char_type == boost::uint32_t? If yes, then I'd like to put the attached patch in and proceed with solution 2) above. With two modifications (include

Re: plain text output - how to proceed

2006-09-04 Thread Peter Kümmel
Georg Baum wrote: > Up to now there have been two proposals how to fix the plain text output: > > 1) from Abdel: Still use narrow streams > > virtual int InsetBase::plaintext(Buffer const &, std::ostream & os, > OutputParams const &) const; > > and implement operators for docstring and char_typ