Re: Fontconfig error

2011-02-26 Thread wolf python london
On 27 February 2011 03:07, Camaleón wrote: > On Sat, 26 Feb 2011 18:22:21 +, Liam O'Toole wrote: > >> On 2011-02-26, Camaleón wrote: > >>> The error is clear: either the file should be corrected (unless the >>> user had manually removed or tweaked the original file) or the output >>> error sho

Re: Fontconfig error

2011-02-26 Thread Camaleón
On Sat, 26 Feb 2011 18:22:21 +, Liam O'Toole wrote: > On 2011-02-26, Camaleón wrote: >> The error is clear: either the file should be corrected (unless the >> user had manually removed or tweaked the original file) or the output >> error should be properly handled. > > The file concerned is

Re: Fontconfig error

2011-02-26 Thread Liam O'Toole
On 2011-02-26, Camaleón wrote: > On Sat, 26 Feb 2011 17:32:16 +, Liam O'Toole wrote: > >> On 2011-02-26, Camaleón wrote: > Now we have just one root element, but that's only a partial solution. The file local.conf should itself be a valid and well-formed XML document. >>> >>> Ye

Re: Fontconfig error

2011-02-26 Thread Camaleón
On Sat, 26 Feb 2011 17:32:16 +, Liam O'Toole wrote: > On 2011-02-26, Camaleón wrote: >>> Now we have just one root element, but that's only a partial solution. >>> The file local.conf should itself be a valid and well-formed XML >>> document. >> >> Yes, and that's why I suggested the user to

Re: Fontconfig error

2011-02-26 Thread Liam O'Toole
On 2011-02-26, Camaleón wrote: > On Sat, 26 Feb 2011 16:15:51 +, Liam O'Toole wrote: > >> On 2011-02-26, Camaleón wrote: > >>> You can open a new report, I also think the error is about "local.conf" >>> formatting that XML parser does not like. The error you are getting is >>> gone if you encl

Re: Fontconfig error

2011-02-26 Thread Camaleón
On Sat, 26 Feb 2011 16:15:51 +, Liam O'Toole wrote: > On 2011-02-26, Camaleón wrote: >> You can open a new report, I also think the error is about "local.conf" >> formatting that XML parser does not like. The error you are getting is >> gone if you enclose the whole XML file inside a parent t

Re: Fontconfig error

2011-02-26 Thread Liam O'Toole
On Sat, 26 Feb, 2011 at 21:32:41 +0800, wolf python london wrote: > On 26 February 2011 17:48, Liam O'Toole wrote: > > On 2011-02-26, wolf python london wrote: > >> Hey all: > >> > >> I'm using Debian Squeeze .When I open a gvim from the terminal ,I

Re: Fontconfig error

2011-02-26 Thread Liam O'Toole
On 2011-02-26, Camaleón wrote: > El 2011-02-26 a las 21:36 +0800, wolf python london escribió: > > (resending to the list) > >> On 26 February 2011 21:09, Camaleón wrote: > >> >> Fontconfig error: "local.conf", line 6: junk after document eleme

Re: Fontconfig error

2011-02-26 Thread Camaleón
El 2011-02-26 a las 21:36 +0800, wolf python london escribió: (resending to the list) > On 26 February 2011 21:09, Camaleón wrote: > >> Fontconfig error: "local.conf", line 6: junk after document element > >> > >> > >> I check the /etc/fonts

Re: Fontconfig error

2011-02-26 Thread Camaleón
On Sat, 26 Feb 2011 17:39:25 +0800, wolf python london wrote: > I'm using Debian Squeeze .When I open a gvim from the terminal ,I get an > error > > Fontconfig error: "local.conf", line 6: junk after document element > > > I check the /etc/fonts/local.conf a

Re: Fontconfig error

2011-02-26 Thread Liam O'Toole
On 2011-02-26, wolf python london wrote: > Hey all: > > I'm using Debian Squeeze .When I open a gvim from the terminal ,I get an error > > Fontconfig error: "local.conf", line 6: junk after document element > > > I check the /etc/fonts/local.conf and

Fontconfig error

2011-02-26 Thread wolf python london
Hey all: I'm using Debian Squeeze .When I open a gvim from the terminal ,I get an error Fontconfig error: "local.conf", line 6: junk after document element I check the /etc/fonts/local.conf and cannot find what's worong . I put the local.conf here(https://gist.github.com/

fontconfig error

2003-10-25 Thread LeVA
Hello! I just wanted to ask, if someone knows what does this message mean: Fontconfig error: Cannot load default config file I get this message whith _all_ of the kde apps. Anyway, I don't notice any failure in the application's fonts. Is this a serious error message? How can I fix th