Les,
 
I have a customer case:
 
418342 areva AR59217Locale set aborts, Locale setSystemLocaleTo: #C looses the setting when image is re-started.
 
 
Can somebody have a look?
 
Thanks and best regards,
Janos
 
 
From: [hidden email] [[hidden email]] On Behalf Of Kooyman, Les
Sent: Monday, February 15, 2010 11:24 PM
To: Jan Weerts; Knight, Alan
Cc: VWNC List
Subject: Re: [vwnc] Fonts in Linux
 
Are there still examples of VW 7.7 not starting at all on certain LINUX distributions (with their standard installed fonts)?
 
If I introduce the request that we consider only LINUX distributions no older than 3 years in our problem set, is this still an issue?
 
To be fair, it's more than just a question of VW being "picky" about its fonts, when it won't start up at all, it has failed various sanity checks including #C locale with US-ASCII encoding. This shouldn't be happening on modern LINUX systems at all at this point. If it is, I'd like to know about it.
 
Handling this issue consistently (on reasonable distributions, no SLS 0.99 please) is an important precursor to improving font support overall.
 
Les Kooyman
Cincom
 

---

From: [hidden email] on behalf of Jan Weerts
Sent: Mon 2/15/2010 12:49 AM
To: Knight, Alan
Cc: VWNC List
Subject: Re: [vwnc] Fonts in Linux

Hi Alan!

Alan Knight wrote:
> We would like to do an update of the X11 fonts (and of various
> other things about the font system in general) but we do not at
> this point having a schedule we're willing to commit to.
>
> I'm curious exactly what you're looking for in fonts.

The question was not directed to me, but I also have one or two wishes
concerning fonts. Here the most frustrating aspect of VW font handling
on Linux: for me is its tendency to totally refuse to start up on
certain X window managers. I do not say, that these are always
configured correctly, but I have never seen a pickier primadonna
application that does not even start up, when its favorite fonts are
somehow broken. One could argue, that the environment needs to be
correct to function correctly, but I wonder, why other applications
are not so picky and why VW is not even capable of logging its problem
in a way, that indicates to a user of the app (usually not the
administrator of the machine), what the problem is.

These kinds of problems date back (at least for us) to 2003, the last
incarnation about a week ago with a 7.6 app and an Exceed X server.
One culprit seemed to be ArborTextAttributes>>updateLineGridding and
the bowels thereof. After capturing errors here, something else blew
up and we changed the X server, because we ran out of time for further
diagnosis and patching.

I consider this basics. Since I am not a regular VW-on-Linux user the
pixeled fonts do not annoy me often enough, so this point does not
make it to the same priority as startup problems. But as an indicator:
in this shop all the regular (as in every day) developers on VW use
Windows, while irregular VW developers use 40% Windows and 60% Linux.

Regards
   Jan

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc