A couple of weeks ago I changed my locale from C to en_US.UTF-8. This allows me to see European-language accents in alpine, but it's screwed up my regular text editor (used to compose messages, too), 'joe.' Somehow, now there's a 'X' after each period in messages apparently written with Outlook when they are quoted in a reply. I'll deal with that issue shortly.
The other interesting and unintended side effect is that my spreadsheet application, XessSE, no longer responds to a file open command. Yes, there are alternatives, particularly OO.o, but I bought a couple of licenses for XessSE a dozen years ago and it's perfect for my needs. The issue is locale related. I spent time on the phone this afternoon with the company president (he's one of the two original developers) and he identified the problem. While they've moved their enterprise version, Xess, to version 6, the SE remains frozen at version 5. Version 6 allows the use of most locales, even multiple ones at the same time. They never added this capability to the SE version 5. One suggestion he had was to wrap the command to invoke the application so that it perceives the LANG to be 'C' rather than en_US.UTF-8. Can someone point me toward a way of writing such a wrapper script? I'm not sure what search term(s) to use in Google to see if a solution can be found there. Rich _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
