headers
Angus Leeming | 1 Mar 2006 04:33
Favicon

Re: Problem with INSTALL.Win32 -

Joost Verburg <joostverburg <at> ...> writes:
> Thanks for these detailed instructions. Maybe it would be a good idea to 
> update the old build_lyxwin script to automate parts of the process. If 
> this is not going to happen, make sure that it's removed so it won't 
> confuse people.

I'll try and do so tomorrow.

Angus

ps Michael, Vielen Dank!
Permalink | Reply | 0 comments |
headers
Uwe Stöhr | 1 Mar 2006 10:23
Picon

Re: Lyx/Win does not accept characters in non-english encoding!

 > Uwe Stöhr wrote:
 >
 >>> It seems like Lyx/Win uses KOI8-R
 >>> even when LANG is explicitly assigned to "ru_RU.CP1251".
 >
 >> This should be fixed in version 1.0 and 1.1 of this installer:
 >
 > I use 1.1. It still exists.

To get it to work you need to set your win locale settings to russian 
(date format and keyboard layout), because it will only work when 
Windows starts with the codepage CP 1250 as default.

 >>> Second, when keyboard is switched to russian layout,
 >>> Lyx ignores all keys until keyboard is switched back to english.
 >>
 >> What do you mean with "keyboard switch"?
 >
 > Pressing Alt+Shift or Ctrl+Shift for switching
 > between typing of english and russian characters.
 >
 >> Are you using a russian windows with a russian keyboard
 >
 > English Windows with Russian MUI.
 >
 >> and you can't insert cyrilic characters?
 >
 > Yes. They are simply ignored - LyX does nothing
 > when I press keys in russian layout.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Uwe Stöhr | 1 Mar 2006 10:27
Picon

Re: Lyx/Win does not accept characters in non-english encoding!

 > You mean that you're making changes to the LyX code/support files?
 > That's bad. All such changes should go into the LyX repository.

I only changed the encoding of the russian .po-file from ISO to windows 
CP 1250 and compiled a .mo from this.
This should fix the problems as users reported this to me.
I asked on the list to have two different .po files, one in ISO and one 
  in Windows CP, but this proposal was rejected.

regards Uwe
Permalink | Reply | 7 comments |
headers
Lars Gullik Bjønnes | 1 Mar 2006 11:16

Re: Lyx 1.4 matbb/mathcal/mathrm issue

Martin Vermeer <martin.vermeer@...> writes:

| On Tue, Feb 28, 2006 at 07:43:23PM +0100, Georg Baum wrote:
| > Am Dienstag, 28. Februar 2006 18:44 schrieb Martin Vermeer:
| > 
| > > OK if I commit this? It's your fix as much as mine
| > 
| > Yes, of course.
| 
| Done.

Good. I will create the branch later today then.

--

-- 
	Lgb
Permalink | Reply | 0 comments |
headers
Beck, Andrew Thomas - BECAT001 | 1 Mar 2006 11:49
Picon
Picon

RE: Source cosmetics

People have talked about preferences for a lyx namespace and/or
prefixes, but nobody has really explained why either is needed. IMHO, 
Lyx is never going to be a library to be linked with some other
application - it's simply not written that way. So I don't see 
what it is that we need to separate from.

I think the CamelBump style is better than underscore_style because
it keeps names shorter. In any case, it's essentially an arbitary 
decision (personally, I generally use camelBump). The 
actual decision is not so important, so long as it's made and applied.

I do think we need to include the virtual descriptor on any overloaded 
method declarations. Obviously it's not required, but it makes it 
clear to anybody traversing the code.

Finally, I think it's important to keep this fairly minor house-keeping
issue separate from an overall redesign. Something one person can do
in short time.

Andrew
Permalink | Reply | 2 comments |
headers
Jean-Marc Lasgouttes | 1 Mar 2006 11:53
Picon
Picon
Favicon

Re: Lyx/Win does not accept characters in non-english encoding!

>>>>> "Uwe" == Uwe Stöhr <uwestoehr@...> writes:

>> You mean that you're making changes to the LyX code/support files?
>> That's bad. All such changes should go into the LyX repository.

Uwe> I only changed the encoding of the russian .po-file from ISO to
Uwe> windows CP 1250 and compiled a .mo from this. This should fix the
Uwe> problems as users reported this to me. I asked on the list to
Uwe> have two different .po files, one in ISO and one in Windows CP,
Uwe> but this proposal was rejected.

My answer at the time was that gettext will deliver the text in the
locale you ask for, and will convert as needed as long as iconv
support is compiled in. Does it find iconv when configuring?

JMarc
Permalink | Reply | 5 comments |
headers
João Luis Meloni Assirati | 1 Mar 2006 12:20
Picon
Picon

DVI search.


Hello,

Now that lyx is very close to a release, I publish again in this list my dvi 
search patch. I intend to maintain this patch for all releases of the 1.4 
series as long as it remain useful to me. I hope that it can be useful to 
others too, and that's why I am sending it to this list and will send it to 
lyx-users when 1.4 come out. As in previous times, any comment, suggestion or 
bug report will be very welcome.

Below are some instructions on how to configure and use the feature.

Regards,
Joao.

---------------------------------------------------------------

Configurig lyx:
After applying the patch and recompiling lyx, add the following lines to your  
preferences file:

\source_specials_switch "-src-specials"
\dvi_fwsearch_switch "auto"

That should work with xdvi and kdvi.

(If you use another dvi viewer, you must supply a true command line switch 
instead of auto. You should be able to figure out what it is by comparing 
with the explicit line for xdvi:
(Continue reading)

Permalink | Reply | 40 comments |
headers
Lars Gullik Bjønnes | 1 Mar 2006 12:24

Re: Source cosmetics

"Beck, Andrew Thomas - BECAT001"
<Andrew.Beck@...> writes:

| People have talked about preferences for a lyx namespace and/or
| prefixes, but nobody has really explained why either is needed. IMHO, 
| Lyx is never going to be a library to be linked with some other
| application - it's simply not written that way. So I don't see 
| what it is that we need to separate from.

Libs that do not have its stuff in namespaces.

And that lyx will never be a library can be argued.
(I have some prelim work to make the lyx 'core' a lib for the
frontends.)

| I think the CamelBump style is better than underscore_style because
| it keeps names shorter. In any case, it's essentially an arbitary 
| decision (personally, I generally use camelBump). The 
| actual decision is not so important, so long as it's made and applied.
| 
| I do think we need to include the virtual descriptor on any overloaded 
| method declarations. Obviously it's not required, but it makes it 
| clear to anybody traversing the code.
| 
| Finally, I think it's important to keep this fairly minor house-keeping
| issue separate from an overall redesign. Something one person can do
| in short time.

You should read the code guidelines that we have, it is not extensive
but covers the important parts.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Uwe Stöhr | 1 Mar 2006 12:40
Picon

Re: Lyx/Win does not accept characters in non-english encoding!

Jean-Marc Lasgouttes wrote:

> My answer at the time was that gettext will deliver the text in the
> locale you ask for, and will convert as needed as long as iconv
> support is compiled in. Does it find iconv when configuring?

This is the problem: The iconv version available for windows seems to be 
buggy, so that I had to do this manually. (iconv for windows was also 
not able to convert documents from/to utf)
But maybe I did something wrong.

regards Uwe
Permalink | Reply | 0 comments |
headers
Angus Leeming | 1 Mar 2006 12:45
Favicon

Re: Lyx/Win does not accept characters in non-english encoding!

Jean-Marc Lasgouttes <Jean-Marc.Lasgouttes <at> ...> writes:
> My answer at the time was that gettext will deliver the text in the
> locale you ask for, and will convert as needed as long as iconv
> support is compiled in. Does it find iconv when configuring?

My understanding is that Uwe has always used my executable, so you're probably
asking the wrong man :)

Michael's post last night has just kickstarted me into trying to build LyX on
Windows again. I've upgraded my MinGW/MSYS environment and installed gettext and
libiconv. I'm currently building Qt (as a .dll rather than as a static library).

When I get to the configure LyX stage I'll see if I can use the installed
gettext/libiconv rather than the gettext that comes with the LyX sources.

Angus
Permalink | Reply | 3 comments |

Gmane