Re: Another configure.py issue

On Thu, Aug 03, 2006 at 10:10:25PM +0200, Uwe Stöhr wrote: > Bo Peng wrote: > > > I see what you are saying, but stdout will be hidden with the new > > releases so there is even no way to turn on that black command window. > > I currently can do this by running this batch file: > > cd C:\progra

Re: Another configure.py issue

Bo Peng wrote: I see what you are saying, but stdout will be hidden with the new releases so there is even no way to turn on that black command window. I currently can do this by running this batch file: cd C:\programs\LyX14\Resources\$\r$\n\ C:$\r$\n\ "C:\programs\LyX14\bin\python.exe" confi

Bug or correct behavior?

Hi all, I was about to enter this in bugzilla as a minor bug, but decided I'd better check whether the consensus is that it is actually correct behavior. In most dialogs (for instance, Tools->Preferences...), if you select Apply and then Ok the changes are applied. In the text style dialog,

Re: [PATCH] Add more controls to the view source dialog.

> Bo Peng <[EMAIL PROTECTED]> writes: > > This is what makeLatexFile is doing Do you want to change the > > name of those functions as well? Any suggestion? > > generateLatex, generateAscii, generateDocbook... If you look at buffer.h, we also have writeFileAscii(filename...), writeFileAscii(

Re: [PATCH] Add more controls to the view source dialog.

On 8/3/06, Angus Leeming <[EMAIL PROTECTED]> wrote: Bo Peng <[EMAIL PROTECTED]> writes: > This is what makeLatexFile is doing Do you want to change the > name of those functions as well? Any suggestion? generateLatex, generateAscii, generateDocbook... If you look at buffer.h, we also have

Re: [PATCH] Add more controls to the view source dialog.

Bo Peng <[EMAIL PROTECTED]> writes: > This is what makeLatexFile is doing Do you want to change the > name of those functions as well? Any suggestion? generateLatex, generateAscii, generateDocbook... Angus

Re: Patch for lyx2lyx to support utf-8

José Matos <[EMAIL PROTECTED]> writes: | On Thursday 03 August 2006 15:11, Lars Gullik Bjønnes wrote: | > Jose' Matos <[EMAIL PROTECTED]> writes: | > | > [...] | > | > |   When I referred before I was talking about using ucs-4 and ucs-2 for | > | the external format. | > | > That has never been an

Re: Patch for lyx2lyx to support utf-8

On Thursday 03 August 2006 15:11, Lars Gullik Bjønnes wrote: > Jose' Matos <[EMAIL PROTECTED]> writes: > > [...] > > |   When I referred before I was talking about using ucs-4 and ucs-2 for > | the external format. > > That has never been an option. So what about uft-16? ;-) > |   I propose to

Re: Patch for lyx2lyx to support utf-8

Jose' Matos <[EMAIL PROTECTED]> writes: [...] | When I referred before I was talking about using ucs-4 and ucs-2 for the | external format. That has never been an option. | I propose to leave the inputencoding in the file. After all xml allows it | there, so why should not we? We should

Re: Patch for lyx2lyx to support utf-8

On Thursday 03 August 2006 14:44, Lars Gullik Bjønnes wrote: > Right. The internal format (which will be ucs-4, unless somehting > happens) has little or nothing to do with the external format. I know and that is how it work in python as well, the internal representation is ucs-4. Not that I ca

Re: [PATCH] Add more controls to the view source dialog.

You change the signatures of some functions (makeXXXFile), and by doing this the name of the function is now "meaningless". makeXxxxFile(ostream & os, ...) is not making a file anymore, is is just outputting to a stream. IMO the names of these functions should change as well. This is what make

Re: Patch for lyx2lyx to support utf-8

Jose' Matos <[EMAIL PROTECTED]> writes: | On Thursday 03 August 2006 14:26, Lars Gullik Bjønnes wrote: | > IMHO we should drop \inputencoding from the fileformat when moving to | > utf-8, it is not as if you have a choice... | | Such as it is the code supports ucs-4 and ucs-2, but I think that

Re: Patch for lyx2lyx to support utf-8

On Thursday 03 August 2006 14:26, Lars Gullik Bjønnes wrote: > IMHO we should drop \inputencoding from the fileformat when moving to > utf-8, it is not as if you have a choice... Such as it is the code supports ucs-4 and ucs-2, but I think that I agree that we can use utf-8 as the ("de facto")

Re: Patch for lyx2lyx to support utf-8

Jose' Matos <[EMAIL PROTECTED]> writes: | Index: lyx_1_5.py | === | --- lyx_1_5.py(revision 14537) | +++ lyx_1_5.py(working copy) | @@ -216,6 +216,15 @@ | i = i + 1 | | | +def convert_utf8(document): | +

Patch for lyx2lyx to support utf-8

Hi, the following patch adds support for a fictitious file format called 249 which has the property that file encoding is utf-8. The revert part is more difficult. I should revert to the encoding associated with the language, and then verify each character to guarantee that we

Re: [PATCH] Add more controls to the view source dialog.

"Bo Peng" <[EMAIL PROTECTED]> writes: | Dear list, | | Attached patch adds to the view-source dialog (qt3/4): | | 1. 'automatic update' check box. If unchecked, stop automatic updating | of the view source dialog. This is useful for slow machines, and when | full source is displayed. | 2. update