results/problems (Re: [PATCH] Copy/Paste non-ascii characters)
Jay Smith
jay@JaySmith.com
Sat Oct 18 20:50:00 GMT 2003
Harold,
I have done the installation and I have several things to report. If some
of these are not for this list, please advise. First of all, FYI, when I
did the install, Progeny would not respond at all so I used Purdue. In any
case, I turned OFF everything and then turned on only XFree xserve,
scalable fonts, and xwinclip -- those of course caused some other things to
turn on automatically.
1) The main problem of copy/paste of non-ascii characters *within* Linux
Mozilla seems to be *fixed*. Thanks!
However....
2) I had my own modified script (with its own unique filename) that was
used to start X; I guess this was before startxdmcp.bat was available. I
copied my script into place. However, when I run MY script now, it seems
like the command (in MY script)
start XWin -nodecoration -clipboard -once -query jsa.jaysmith.com
actually (also?) RUNS startxdmcp.bat
That is very odd and I am not sure what to do. I had to modify
startxdmcp.bat to bring it in line with my script so the proper command
would get done.
I believe that startxdmcp.bat is getting run because the DOS box that
appears says so, identifying it by name -- even if *I* don't directly run it.
3) I think that startxdmcp.bat may have an error in it. The original
version of it has the command:
start XWin -query %REMOTE_HOST% -nodecoration -lesspointer
and this causes an error in the DOS box about "too many paramaters". I
am certainly no expert, but I think that the "-query ...." should be the
LAST thing on the command line. Anyway, when I made it so (like my
original script) it worked without putting out the error.
4) Generally X performance seems to be better. It is very subjective, but
so good, so far.
Jay
Harold L Hunt II said the following on 10/14/2003 10:28 PM:
> Jay,
>
> The status is that XFree86 has been recompiled and rereleased for Cygwin
> 1.5.x. Everything should be "safe". However, I would always recommend
> doing a demo installation on one machine and trying out your apps before
> you upgrade all machines. That should give you a better idea of if it
> will work for you.
>
> One thing you can do is rename c:\cygwin to c:\cygwin_works, download
> setup.exe to c:\cyginstall_test, then run setup.exe and install to
> c:\cygwin (which is now an empty directory). This will allow you to
> test a complete new install and see if it works for you. You can then
> move c:\cygwin to c:\cygwin_test and move c:\cygwin_works back to
> c:\cygwin to restore your old installation.
>
> Harold
>
> Jay Smith wrote:
>
>> Harold,
>>
>> Before I embark on upgrading all of Cygwin to deal with this, is there
>> any risk that stuff will break? Since Cygwin underwent a major
>> overhaul recently, it seems to me that there is a chance that some
>> small parts of XFree86 stuff (I use little else) might be broken until
>> all is brought up to speed.
>>
>> Since this is a minute-to-minute critical application (X windowing)
>> upon which we rely 100%, I have to be very careful about changes.
>> (Recalling recent RedHat library changes which broke lots of stuff and
>> recent Perl version changes which wrecked our CGI scripts.)
>>
>> What is the status? Does all the XFree86 stuff work under the new
>> Cygwin? Is it "safe" now? (I know that in the first few weeks it was
>> not "safe".)
>>
>> Jay
>>
>> Harold L Hunt II said the following on 10/14/2003 09:23 PM:
>>
>>> Jay,
>>>
>>> Jay Smith wrote:
>>>
>>>> Harold,
>>>>
>>>> a) Before I attempt this fix, will this work with my old version of
>>>> everything else? I know that Cygwin has moved ahead since April.
>>>> Or does installing this start me down a slippery slope...
>>>
>>>
>>>
>>>
>>> I hate when I forget to ask this if people are running the latest
>>> version or not. You really need to be running the latest versions in
>>> order for us to properly debug and test things.
>>>
>>> Yes, you will have to update to the 4.3.0 release of Cygwin/XFree86.
>>> I think I released it after April. All of the DLLs have had their
>>> names changed, so you need to get those (in the -bin package) but I
>>> believe I made the fonts in such a way that they will not download
>>> again unless you have a really old version. You will basically need
>>> to get anything that has a new version, since there have been updates
>>> to Cygwin's DLL, various libraries, etc.
>>>
>>>> b) Before I had the sense to ask the question above, I got as far as
>>>> starting the download process from a mirror that I had previously
>>>> used. The setup program warned me that a newer setup.ini file would
>>>> replace the old one, but did not seem to give me a way to cancel
>>>> out. So, now I have an new setup.ini but old "everything else"
>>>> files -- and I *do* need the "old everything else" to reinstall on
>>>> PCs that die, etc. Am I screwed?
>>>
>>>
>>>
>>>
>>> Setup gives a warning about setup.ini telling it that there is a new
>>> version of setup.exe available and that you don't have it. Download
>>> the latest setup.exe and you won't get the warning (plus there has
>>> been a lot of development on setup.exe in the last several months).
>>>
>>> I'm not sure about the status of your installation images. It sounds
>>> like you have been doing a download to disk then installing from
>>> that? Uh... guess all I can tell you is that you should have backed
>>> up first :) Of course, you could just look at files that have been
>>> updated recently and check if setup.exe made a backup of the old
>>> setup.ini that you had.
>>>
>>> Harold
>>>
>>>
>>>> Jay
>>>>
>>>>
>>>> Harold L Hunt II said the following on 10/12/2003 11:01 PM:
>>>>
>>>>> Jay,
>>>>>
>>>>> I just posted XFree86-xserv-4.3.0-20 as a 'test' package; it should
>>>>> be showing up on mirrors within a few hours. When it does, run
>>>>> setup.exe and manually select version '4.3.0-20' for the
>>>>> XFree86-xserv package. Then, run the new server version as usual
>>>>> (do not use the new flag that Kensuke talked about) and report your
>>>>> results to the mailing list.
>>>>>
>>>>> Harold
>>>>>
>>>>> Jay Smith wrote:
>>>>>
>>>>>> Dear Kensuke,
>>>>>>
>>>>>> Thank you very much for your effort on this.
>>>>>>
>>>>>> Unfortunately, I am pretty ignorant of these matters, thus you
>>>>>> will have to tell me what it is that I should do with the two
>>>>>> .diff files you attached. I will be happy to do whatever with
>>>>>> them, but I am clueless as to what is to be done with them.
>>>>>>
>>>>>> Sorry to be a pain.
>>>>>>
>>>>>> Jay
>>>>>>
>>>>>> Kensuke Matsuzaki said the following on 10/12/2003 09:33 PM:
>>>>>>
>>>>>>> Jay,
>>>>>>>
>>>>>>> Perhaps this patch enable XWin to copy/paste non-ascii characters
>>>>>>> even if Windows does't support Unicode (95/98/Me).
>>>>>>> LANG environment variable and Windows locale must be same.
>>>>>>> I added -nounicodeclipboard option, I tested using this on XP.
>>>>>>> But I don't have 95/98/Me.
>>>>>>>
>>>>>>> And it seems tha libX11 has some CTEXT convertion bug, I attach
>>>>>>> patch that based on TAKABE's work.
>>>>>>> http://www.ff.iij4u.or.jp/~t-takabe/xf410_xim_fix.diff
>>>>>>>
>>>>>>> By the way, nls/locale.alias has alias somethig like
>>>>>>> "Arabic_Egypt.1256". Can we use that?
>>>>>>> If so, we no longer need LANG environment variable.
>>>>>>> We can get it following code.
>>>>>>>
>>>>>>> char pszCountry[128];
>>>>>>> char pszLanguage[128];
>>>>>>> int nAcp = GetACP ();
>>>>>>> GetLocaleInfo (LOCALE_SYSTEM_DEFAULT, LOCALE_SENGCOUNTRY,
>>>>>>> pszCountry, 128);
>>>>>>> GetLocaleInfo (LOCALE_SYSTEM_DEFAULT, LOCALE_SENGLANGUAGE,
>>>>>>> pszLanguage, 128);
>>>>>>>
>>>>>>> printf ("%s_%s.%d\n", pszLanguage, pszCountry, nAcp);
>>>>>>>
>>>>>>> Kensuke Matsuzaki
--
Jay Smith
e-mail: Jay@JaySmith.com mailto:Jay@JaySmith.com
website: http://www.JaySmith.com
Jay Smith & Associates
P.O. Box 650
Snow Camp, NC 27349 USA
Phone: Int+US+336-376-9991
Toll-Free Phone in US & Canada:
1-800-447-8267
Fax: Int+US+336-376-6750
More information about the Cygwin-xfree
mailing list