[developers] Contents of developers Digest, Vol 85, Issue 1

Stephan Oepen oe at ifi.uio.no
Wed May 23 19:27:25 CEST 2012

no, i have no idea; in fact was surprised to hear the two build universes yield different results with regards to font handling.

i would suspect the ACL versions and patch levels used to build could be different; is the version you use (at UW) for the LinGO builds fully patched?  the LOGON builds should have all patches as of sometime last fall.

or 32- vs. 64-bit, as LinGO is only 32-bit, while most LOGON users likely run on 64-bit environments.

or more subtle properties of the build host, e.g. which Motif and X11 versions are installed?  which reminds me, the LinGO build packages a few X11 shared libraries, i believe (no access to the source tree tonight).  those should be synchronized to what is used at build time, i.e. on the build host.

that's about all i can guess at this point, i'm afraid :-).

best, oe

On 23. mai 2012, at 19:07, "Emily M. Bender" <ebender at uw.edu> wrote:

> I also had some students try to install the DELPH-IN build this quarter
> and run into the same problem.
> We (David Brodbeck and I) would like to update the DELPH-IN build
> (or, failing that, the installation instructions) so as to resolve this problem,
> but we need some guidance on how to proceed.  Is this something that
> is likely rooted in the build process or the code somewhere?  Does anyone
> have any insight on why the LOGON and DELPH-IN builds are behaving
> differently in this regard?
> Thanks,
> Emily
> On Mon, May 21, 2012 at 2:02 AM, Yi Zhang <yzhang at coli.uni-sb.de> wrote:
>> hi,
>> just for a bit of context of the font problem: the recent reports of the issue were mostly generated by CoLi students in my Grammar Engineering class, where they were instructed to use the DELPH-IN build of LKB instead of LOGON. on fresh installations of Ubuntu (12.04 & 11.10 LTS) with the latest build (2012-02-17), strange asian fonts were used as fallback for the LKB Top window menu, making them unreadable (even for asians). on a Fedora 16 installation, no suitable fallback font were found, and LKB Top window fails to show up at all.
>> after comparing the list of available x fonts on Liling's Ubuntu (where a decent fallback font was found) with my fresh installations, i find the following font packages will temporary fix the asian font issue:
>> $ sudo apt-get install xfonts-100dpi xfonts-75dpi
>> there are still tons of font fallback warnings, but the menu items are at least readable. i hope this can be a temporary workaround for people using Ubuntu and the latest DELPH-IN builds.
>> as Francis pointed out, there is no such font issue with the LOGON build (on both of my Ubuntu installations, LOGON starts fine without font warning). maybe some one can look into the issue in the future builds of LKB?
>> cheers,
>> yi
>> On May 20, 2012, at 6:56 AM, Francis Bond wrote:
>>> G'day,
>>> How are you installing the lkb?   I did a fresh LOGON installation on
>>> a new ubuntu machine (Ubuntu 12.04 LTS) and after following the
>>> instructions on the LogonUbuntu page (adding the ia32 libraries and
>>> libjpeg62) the lkb started up fine with "M-X logon".
>>> With "(rsa "erg")" I was able to load the ERG and then parse things
>>> with no problems.  This was a completely fresh install, with the only
>>> extra additions being Emacs23, libre office and the Battle for Wesnoth
>>> (it's on Arthur's machine :-).
>>> Jacy, on the other hand, fails to parse, with several messages about
>>> "malformed empty difference list"s.  Someone (me) will fix this
>>> soonish.
>>> --
>>> Francis Bond <http://www3.ntu.edu.sg/home/fcbond/>
>>> Division of Linguistics and Multilingual Studies
>>> Nanyang Technological University
> -- 
> Emily M. Bender
> Associate Professor
> Department of Linguistics
> Check out CLMS on facebook! http://www.facebook.com/uwclma

More information about the developers mailing list