lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Lines to edges of \center-column


From: David Wright
Subject: Re: Lines to edges of \center-column
Date: Mon, 24 Apr 2017 23:49:40 -0500
User-agent: Mutt/1.5.21 (2010-09-15)

On Mon 24 Apr 2017 at 21:35:48 (+0200), address@hidden wrote:
> Seems the latest devel version (2.19.59) has fixed that bug, so it's
> probably not important anymore.
> 
> On 04/24/17 19:43, David Wright wrote:
> >Well, I can't take a view on that because AFAICT the source in the OP
> >only contained kanji (complicated-looking) characters. Would that be
> >correct? Could you give the source with which you produced your
> >seam.png output (preferably as an attachment so I don't have to rely
> >on my paste's behaviour).
> 
> Sure, attached. (The two japanese words are "kana" and "kanji".)
> >I agree, but I'm more concerned about the contents of the window than
> >the window itself.
> 
> That's true, but ugly chrome can be rather distracting.

I don't know what chrome is.

> >Well, I've taken a closer look with evince at my box.pdf and I can see
> >the effect you mention. However, I think they're just artifacts of its
> >display, because when you magnify the areas in question, the blemishes
> >don't get magnified but disappear, or appear elsewhere. So I don't
> >think the problem lies in the PDF at all. One also has to bear in mind
> >that the screen resolution can lead to odd effects just because of
> >where the grid of pixels happen to be relative to the image.
> 
> Yeah, I'm pretty sure those gaps are just some kind of rounding error.
> 
> >Are those characters the same height? I think you should put some
> >characters into both lines for control purposes; some ordinary Roman
> >alphabeticals, say.
> 
> I'm pretty sure they are, assuming they use the same font. Oddly
> enough, manually specifying the font fixes it (tested with Takao
> Gothic and Takao Mincho). The Japanese characters look identical
> with and without manual font override, but the boxes don't.
> 
> I'm guessing it's just some weird font bug, which is fixed in 2.19.

Looking back at your seam.png, and at my output from the modified LP
that you posted, I would guess that different fonts were used for the
two lines. Now the actual thicknesses aren't defined, though HEAVY
will presumably be at least as thick as normal. But what might affect
you is if one of your fonts is, for some reason, doing some sort of
double-width operation.

IOW is it possible that something looks at a double-width font
and decides to pull out the matching double-width box characters
to put alongside it? This decision could have been made differently
for the two fonts/character sets you were using, hence one set of
lines being roughly twice as long as the other. The easiest way
to test this might be with box characters that are not just simple
horizontals, ie using characters like ┳ and ╔.

> By the way, is it possible to have both 2.18 and 2.19 installed at
> the same time (preferrably with 2.19 as the default `lilypond`), on
> Arch Linux? Having to uninstall and then recompile if I want to test
> something with 2.18 isn't very fun.

Yes. I don't know which version Arch installs itself, but you can
install as many versions of LP as you like so long as you use prefixes
to distinguish them. Here's my crib for installation. Obviously you
don't uninstall the others if you want several.

✁✂✁✂✁✂✁✂
Uninstall the old development version:

$ (bash) /home/david/lilypond-xxxoldxxx/bin/uninstall-lilypond

This does not remove links in ~/bin, or the ~/bin/lilypond executable,
because of the copying shown below.

Install the newly downloaded one:

$ cd ~
$ bash .../lilypond-xxxnewxxx.linux-x86.sh --prefix lilypond-xxxnewxxx

Copy links in ~/lilypond-xxxnewxxx/bin/ and  ~/lilypond-xxxnewxxx/bin/lilypond
into ~/bin/, overwriting the old ones there.
✃✂✃✂✃✂✃✂

~/bin/ is in my $PATH, of course, which handles my defaulting version,
but you can use the various versions ~/lilypond-xxxnewxxx/bin/lilypond
directly, or give them more convenient aliases.

Cheers,
David.

Attachment: jp.png
Description: PNG image


reply via email to

[Prev in Thread] Current Thread [Next in Thread]