ubuntu-x-swat team mailing list archive

[Michael Jones <eternalorb@xxxxxxxxx>]

Martin
    I absolutely agree with you.

    I look at the situation like this,
    linux, in all of its various flavors, are free. Who am I to complain
when something I got for free doesn't work 100% right all the time.

    If theres a better solution to this issue, or any others.. by delivering
the cure instead of treating the symptoms of any of them, I am all for it
and willing to help in any way I am able.

-Mike

On Sat, May 9, 2009 at 6:27 PM, Martin Olsson <mnemo@xxxxxxxxxx> wrote:

> xorg.conf is ASCII today afaik so it could be converted to UTF-8 in a
> backwards compatible fashion. Once that's done you could implement a
> small check that detects this and prints a nice error or even accepts
> the non-"ASCII 34" double quotes.
>
> I think a lot of people feel that fixing the quotes would be like
> "treating the symptoms" instead of "finding the cure". The real fix is
> to make sure that no xorg.conf editing should be necessary for any
> mainstream use case at all. Lots of people are working very hard at
> getting to that point and just in X server release 1.6.0 we made
> enormous progress.
>
> ** Summary changed:
>
> - xorg can't handle the character: ”
> + xorg doesn't recognize the non-ASCII variant of character ” in xorg.conf
>
> --
> xorg doesn't recognize the non-ASCII variant of character ” in xorg.conf
> https://bugs.launchpad.net/bugs/373516
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “xorg-server” source package in Ubuntu: New
>
> Bug description:
> If given the character ” in xorg.conf, X does not work correctly.
>
> The character ” can be found all over the Internet, including in posts
> intended to give advice on how to edit xorg.conf to achieve various goals.
>  ” looks incredibly similar to ".
>
> This is a serious usability concern. I mistakenly gave someone advice
> taking information from the Internet that at first glance looked identical
> to steps I had taken myself, and successfully achieved my goal.
>
>    Either the character ” needs to be changed to look less similar than ",
>    X need to be able to handle the character ”,
>    or some other step needs to be taken.
>
>    From the perspective of anyone but a programmer, a program is expected
> to handle any input its given without crashing. A program is expected to
> handle input its given gracefully, without crashing, or refusing to start.
> And to a user ” is exactly the same, and indistinguishable from ".
>
>
>    I hold no illusions that this issue will ever be fixed, but please don't
> mark this bug as invalid. My laptop is incapable of utilizing dual monitors
> now that the proprietary drivers for my ATI card are no longer supported by
> ATI without editing xorg manually. One of the first things that I had to do
> when using ubuntu on this machine was edit the xorg.conf file to fix a
> graphics issue.
>    It is far from unrealistic to expect users to put the character ” into
> an xorg.conf file. OpenOffice writer correctly displays the character, and I
> don't find it unrealistic that someone will eventually write a document in
> Word explaining how to do what-have-you in linux to someone. I doubt I'm the
> first to experience this unexpected behavior, and I doubt I'm the last.
>
>    I this that a status of wishlist and confirmed is appropriate for this
> bug. Regardless of if it will ever realistically be fixed, it is still a
> bug.
>
>
> -Mike
>

-- 
xorg doesn't recognize the non-ASCII variant of character ” in xorg.conf
https://bugs.launchpad.net/bugs/373516
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.