From: Will Parsons <varro@nodomain.invalid>
To: cygwin@cygwin.com
Subject: Re: LyX unreadable in 64-bit Cygwin
Date: Thu, 19 Mar 2015 19:20:00 -0000 [thread overview]
Message-ID: <slrnmgm7g1.38o.varro@anukis.local> (raw)
In-Reply-To: <550ACCB3.4020905@gmail.com>
Marco Atzeri wrote:
> On 3/19/2015 12:55 AM, Yaakov Selkowitz wrote:
>> On Wed, 2015-03-18 at 19:45 -0400, Will Parsons wrote:
>>> I recently installed 64-bit Cygwin along side of my 32-bit Cygwin
>>> installation, and find that all the menus show math symbols rather
>>> than text, making LyX unusable. Note that if I specify a file on the
>>> command line, the contents show up fine - it's just the menus/toolbars
>>> that are unreadable. This problem does not happen under 32-bit
>>> Cygwin.
>>
>> I've seen this before on other systems; it just means you need to
>> install some fonts (I just don't remember which atm).
>
> Will,
>
> on my 64 bit system, it works
> and I have only these fonts installed
>
> font-adobe-dpi75 1.0.2-1
> font-adobe-utopia-dpi75 1.0.3-1
> font-alias 1.0.3-1
> font-bh-dpi75 1.0.2-1
> font-bh-lucidatypewriter-dpi75 1.0.2-1
> font-bitstream-dpi75 1.0.2-1
> font-bitstream-type1 1.0.2-1
> font-cursor-misc 1.0.2-1
> font-encodings 1.0.4-1
> font-misc-misc 1.1.1-1
> font-tektronix-misc 2.6-4
> ghostscript-fonts-other 6.0-1
> ghostscript-fonts-std 8.11-1
> texlive-collection-fontsrecommended
>
> Looking at strace output it seems to use only
>
> font-bitstream-type1-1.0.2-1
> font-adobe-dpi75-1.0.2-1
> and its own fonts in
> /usr/share/lyx/fonts/
Thanks. I've installed a few fonts (including adobe and bh), and all
seems to be well now. (As an aside, should LyX pull in some minimal
set as dependencies, or is this not really practicable?)
--
Will
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-03-19 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 23:52 Will Parsons
2015-03-19 0:12 ` Yaakov Selkowitz
2015-03-19 14:09 ` Marco Atzeri
2015-03-19 19:20 ` Will Parsons [this message]
2015-03-19 23:14 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrnmgm7g1.38o.varro@anukis.local \
--to=varro@nodomain.invalid \
--cc=cygwin@cygwin.com \
--cc=gyliamos@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).