Bug#164799: Small typo in generated XF86Config-4

2002-10-16 Thread Warren Turkal
Well, there is actually a library for parsing the config file in xc/programs/Xserver/hw/xfree86/parser . Warren On Wednesday 16 October 2002 11:51 am, [EMAIL PROTECTED] wrote: > On Wed, Oct 16, 2002 at 03:12:51AM -0500, Warren Turkal wrote: > > Would XML be any easier to parse? We could have an X

Bug#164799: Small typo in generated XF86Config-4

2002-10-16 Thread John Lenton
On Wed, Oct 16, 2002 at 03:12:51AM -0500, Warren Turkal wrote: > Would XML be any easier to parse? We could have an XML config file and an > XSLT > to transform it into the real config file. The code to parse the file has got to be somewhere in the xfree source. Somebody probably even knows wher

Bug#164799: Small typo in generated XF86Config-4

2002-10-16 Thread Warren Turkal
Well, there is actually a library for parsing the config file in xc/programs/Xserver/hw/xfree86/parser . Warren On Wednesday 16 October 2002 11:51 am, [EMAIL PROTECTED] wrote: > On Wed, Oct 16, 2002 at 03:12:51AM -0500, Warren Turkal wrote: > > Would XML be any easier to parse? We could have an

Bug#164799: Small typo in generated XF86Config-4

2002-10-16 Thread 164799
On Wed, Oct 16, 2002 at 03:12:51AM -0500, Warren Turkal wrote: > Would XML be any easier to parse? We could have an XML config file and an > XSLT > to transform it into the real config file. We'd still have to reverse the transformation because of all the people who modify their XF86Config-4 fil

Bug#164799: Small typo in generated XF86Config-4

2002-10-16 Thread John Lenton
On Wed, Oct 16, 2002 at 03:12:51AM -0500, Warren Turkal wrote: > Would XML be any easier to parse? We could have an XML config file and an XSLT > to transform it into the real config file. The code to parse the file has got to be somewhere in the xfree source. Somebody probably even knows where.

Bug#164799: Small typo in generated XF86Config-4

2002-10-16 Thread 164799
On Wed, Oct 16, 2002 at 03:12:51AM -0500, Warren Turkal wrote: > Would XML be any easier to parse? We could have an XML config file and an XSLT > to transform it into the real config file. We'd still have to reverse the transformation because of all the people who modify their XF86Config-4 files

Bug#164799: Small typo in generated XF86Config-4

2002-10-16 Thread Warren Turkal
Would XML be any easier to parse? We could have an XML config file and an XSLT to transform it into the real config file. Warren On Tuesday 15 October 2002 09:05 pm, [EMAIL PROTECTED] wrote: > No. It's too hard to parse the file reliably. I've asked for code to > do it; no one has the time and/

Bug#164799: Small typo in generated XF86Config-4

2002-10-16 Thread Warren Turkal
Would XML be any easier to parse? We could have an XML config file and an XSLT to transform it into the real config file. Warren On Tuesday 15 October 2002 09:05 pm, [EMAIL PROTECTED] wrote: > No. It's too hard to parse the file reliably. I've asked for code to > do it; no one has the time and

Bug#164799: Small typo in generated XF86Config-4

2002-10-15 Thread 164799
On Wed, Oct 16, 2002 at 12:42:38AM +0200, Svante Signell wrote: > Can you please give some more information (or a pointer to) how > xserver-xfree86, debconf and dexconf are working together to create > the XFree86-4 file. Sure: $ man 7 debconf $ man dexconf $ sensible-pager /var/lib/dpkg/info/xse

Bug#164799: Small typo in generated XF86Config-4

2002-10-15 Thread 164799
On Wed, Oct 16, 2002 at 12:42:38AM +0200, Svante Signell wrote: > Can you please give some more information (or a pointer to) how > xserver-xfree86, debconf and dexconf are working together to create > the XFree86-4 file. Sure: $ man 7 debconf $ man dexconf $ sensible-pager /var/lib/dpkg/info/xs

Bug#164799: Small typo in generated XF86Config-4

2002-10-15 Thread Svante Signell
Branden, Can you please give some more information (or a pointer to) how xserver-xfree86, debconf and dexconf are working together to create the XFree86-4 file. Every time I install a new version of the xserver, a new XF86Config-4 is created, this error occurs (on more than one computer). Is the o

Bug#164799: Small typo in generated XF86Config-4

2002-10-15 Thread Svante Signell
Branden, Can you please give some more information (or a pointer to) how xserver-xfree86, debconf and dexconf are working together to create the XFree86-4 file. Every time I install a new version of the xserver, a new XF86Config-4 is created, this error occurs (on more than one computer). Is the

Bug#164799: Small typo in generated XF86Config-4

2002-10-15 Thread Branden Robinson
On Tue, Oct 15, 2002 at 10:00:48AM +0200, Svante Signell wrote: > Option "XkbLayout" "se" is the correct setting for Sweden, > not Option "XkbLayout" "sv"! Yes, that's correct. "se" instead of "sv". > This generates problems with some characters, such as |{}[] etc. > Maybe this bug report should

Bug#164799: Small typo in generated XF86Config-4

2002-10-15 Thread Branden Robinson
On Tue, Oct 15, 2002 at 10:00:48AM +0200, Svante Signell wrote: > Option "XkbLayout" "se" is the correct setting for Sweden, > not Option "XkbLayout" "sv"! Yes, that's correct. "se" instead of "sv". > This generates problems with some characters, such as |{}[] etc. > Maybe this bug report shoul

Bug#164799: Small typo in generated XF86Config-4

2002-10-15 Thread Svante Signell
Package: xserver-xfree86 Version: 4.2.0-x, 4.2.1-x Option "XkbLayout" "se" is the correct setting for Sweden, not Option "XkbLayout" "sv"! This generates problems with some characters, such as |{}[] etc. Maybe this bug report should be attributed to debconf since debconf is the program rewriting

Bug#164799: Small typo in generated XF86Config-4

2002-10-15 Thread Svante Signell
Package: xserver-xfree86 Version: 4.2.0-x, 4.2.1-x Option "XkbLayout" "se" is the correct setting for Sweden, not Option "XkbLayout" "sv"! This generates problems with some characters, such as |{}[] etc. Maybe this bug report should be attributed to debconf since debconf is the program rewriting