On 14/12/13 07:14, Urs Liska wrote:
Am 14.12.2013 04:53, schrieb Graham Percival:
On Thu, Dec 12, 2013 at 02:06:38PM +0100, Urs Liska wrote:
The page "GSoC 2012" is obviously outdated.
What should be done with it?
I suggest deleting it. There's no evidence that the proposed
mentors are still
On Fri, 13 Dec 2013 23:05:49 -0800, David Kastrup wrote:
That does not make sense. If you want call-once behavior, you can just
use a callback.
At the moment, the decision on whether to preserve the callback pointer in the
grob property, or fill the property with the returned value, depends
Am 14.12.2013 04:53, schrieb Graham Percival:
On Thu, Dec 12, 2013 at 02:06:38PM +0100, Urs Liska wrote:
The page "GSoC 2012" is obviously outdated.
What should be done with it?
I suggest deleting it. There's no evidence that the proposed
mentors are still available or interested, and those s
"Keith OHara" writes:
>> On Dec 13, 2013, at 9:07 AM, Keith OHara wrote:
>>
>>> Open_type_font:: and Pango_font::name_to_index() each call
>>> FT_Get_Name_Index(). Inserting print statements to trace those
>>> calls I find that FT_Get_Name_Index is called:
>>> 7 times for each character in a Te
On 14/12/13 05:57, Carl Peterson wrote:
On Fri, Dec 13, 2013 at 10:41 PM, Graham Percival
wrote:
On Fri, Dec 13, 2013 at 10:02:23AM -0500, Carl Peterson wrote:
On Thu, Dec 12, 2013 at 7:36 PM, wrote:
I think that the index sidebar colors are too dark. They dominate the
page, in my opinon.
On Dec 13, 2013, at 9:07 AM, Keith OHara wrote:
Open_type_font:: and Pango_font::name_to_index() each call FT_Get_Name_Index().
Inserting print statements to trace those calls I find that FT_Get_Name_Index
is called:
7 times for each character in a Tempo
The layers of functions that result
On Fri, Dec 13, 2013 at 10:41 PM, Graham Percival
wrote:
> On Fri, Dec 13, 2013 at 10:02:23AM -0500, Carl Peterson wrote:
>> On Thu, Dec 12, 2013 at 7:36 PM, wrote:
>> > I think that the index sidebar colors are too dark. They dominate the
>> > page, in my opinon. In the current design, the si
On Fri, Dec 13, 2013 at 03:40:03PM -, Phil Holmes wrote:
> I _think_ the odd place of "web" in the manuals hierarchy is down to
> it being the only part of the documentation that built using "make
> website" - it has something of a split personality between being
> part of the documentation and
On Thu, Dec 12, 2013 at 09:34:28PM +0100, Urs Liska wrote:
> When I go there I can download the whole website as a PDF. OK, this
> makes sense.
> Getting it as one big HTML page also makes sense.
> [but where can I get it in info format?)
We don't provide links to the info documents, because IMO n
On Thu, Dec 12, 2013 at 02:06:38PM +0100, Urs Liska wrote:
> The page "GSoC 2012" is obviously outdated.
>
> What should be done with it?
I suggest deleting it. There's no evidence that the proposed
mentors are still available or interested, and those specific
proposals are a small subject of th
https://codereview.appspot.com/40510046/diff/40001/Documentation/web/download.itexi
File Documentation/web/download.itexi (left):
https://codereview.appspot.com/40510046/diff/40001/Documentation/web/download.itexi#oldcode35
Documentation/web/download.itexi:35: @warningTextBased
Umm, isn't the wh
On Fri, Dec 13, 2013 at 10:02:23AM -0500, Carl Peterson wrote:
> On Thu, Dec 12, 2013 at 7:36 PM, wrote:
> > I think that the index sidebar colors are too dark. They dominate the
> > page, in my opinon. In the current design, the sidebar color and the
> > highlight box fill color are the same.
> I do see how sfnt_get_name_index() does a linear search through the
> font to find a matching name. Much better if LilyPond could look up
> text characters by their Unicode encoding.
Well, there are historic reasons for that. On the other hand, I think
that for lilypond, which often provides
On Fri, 13 Dec 2013 01:38:23 -0800, Werner LEMBERG wrote:
I will check whether I can improve that in FreeType.
Is there a reason this would have such a significantly different
impact in Windows?
No. It's exactly the same code on both platforms. However, for
lilypond, even a single-element
On Thu, 12 Dec 2013 23:07:19 -0800, Keith OHara wrote:
I am happy to say that I was wrong here.
Open_type_font:: and Pango_font::name_to_index() each call FT_Get_Name_Index().
Inserting print statements to trace those calls I find that FT_Get_Name_Index
is called:
7 times for each character
- Original Message -
From: "Urs Liska"
To: "LilyPond Development Team"
Sent: Thursday, December 12, 2013 8:34 PM
Subject: Website questions: Manual->Web
I've raised this issue already, but I think it needs to be considered in
its own thread:
What to do with Manuals->Web?
When I go
- Original Message -
From: "Carl Sorensen"
To: "Phil Holmes" ; "Carl Peterson"
Cc: "Lilypond Dev"
Sent: Friday, December 13, 2013 3:31 PM
Subject: Re: Enable manual-specific styling of documentation; issue
3714(issue 36480048)
On 12/13/13 6:04 AM, "Phil Holmes" wrote:
Thanks fo
Paul Morris wrote
> Usually this works by putting
> http://www.example.com/etc/etc.html";>
> in the
>
> of any non-canonical page, pointing to the canonical page.
Forgot to say: under the scenario of using 301 redirects you wouldn't need
to do any http://lilypond.1069038.n5.nabble.com/Websi
On 12/13/13 6:04 AM, "Phil Holmes" wrote:
>Thanks for what you're doing, but please don't put a lot of images on the
>Google Issue tracker. For bizarre reasons only known to themselves, the
>storage available for attachments is _very_ limited. By accident you've
>just
> used about 1/25 of our r
Urs Liska wrote
> But clicking on "Web (split HTML)" brings you to a copy of the whole
> website, just several directories below the original.
> This is irritating, to say the least.
I agree that this does not make sense for someone browsing the website, and
the text does not really explain what'
On 12/13/13 8:02 AM, "Carl Peterson" wrote:
>On Thu, Dec 12, 2013 at 7:36 PM, wrote:
>> I think that the index sidebar colors are too dark. They dominate the
>> page, in my opinon. In the current design, the sidebar color and the
>> highlight box fill color are the same. Why not keep it th
On Thu, Dec 12, 2013 at 7:36 PM, wrote:
> I think that the index sidebar colors are too dark. They dominate the
> page, in my opinon. In the current design, the sidebar color and the
> highlight box fill color are the same. Why not keep it that way?
Attaching another option, to address your c
- Original Message -
From: "Carl Peterson"
To: "James"
Cc: "Lilypond Dev"
Sent: Friday, December 13, 2013 2:01 PM
Subject: Re: Enable manual-specific styling of documentation;issue
3714(issue 36480048)
On Fri, Dec 13, 2013 at 8:31 AM, James wrote:
On 13/12/13 13:04, Phil Holmes
Carl Peterson writes:
> On Fri, Dec 13, 2013 at 8:31 AM, James wrote:
>> On 13/12/13 13:04, Phil Holmes wrote:
>>
>> Thanks for what you're doing, but please don't put a lot of images on the
>> Google Issue tracker. For bizarre reasons only known to themselves, the
>> storage available for atta
On Fri, Dec 13, 2013 at 8:31 AM, James wrote:
> On 13/12/13 13:04, Phil Holmes wrote:
>
> Thanks for what you're doing, but please don't put a lot of images on the
> Google Issue tracker. For bizarre reasons only known to themselves, the
> storage available for attachments is _very_ limited. By
On 13/12/13 13:04, Phil Holmes wrote:
Thanks for what you're doing, but please don't put a lot of images on
the Google Issue tracker. For bizarre reasons only known to
themselves, the storage available for attachments is _very_ limited.
By accident you've just used about 1/25 of our remaining
Thanks for what you're doing, but please don't put a lot of images on the
Google Issue tracker. For bizarre reasons only known to themselves, the
storage available for attachments is _very_ limited. By accident you've just
used about 1/25 of our remaining quota.
--
Phil Holmes
- Origi
Incorporated most of the comments.
Will upload new patch set in a minute
https://codereview.appspot.com/40510046/diff/20001/Documentation/web/download.itexi
File Documentation/web/download.itexi (right):
https://codereview.appspot.com/40510046/diff/20001/Documentation/web/download.itexi#newcode
>> I will check whether I can improve that in FreeType.
>
> Is there a reason this would have such a significantly different
> impact in Windows?
No. It's exactly the same code on both platforms. However, for
lilypond, even a single-element cache would help, see attached
quick'n'dirty patch (fo
Werner LEMBERG writes:
>> Open_type_font:: and Pango_font::name_to_index() each call
>> FT_Get_Name_Index(). Inserting print statements to trace those calls
>> I find that FT_Get_Name_Index is called:
>> 7 times for each character in a Tempo
>> 5 times for each character in a Text Script
>> ...
> Open_type_font:: and Pango_font::name_to_index() each call
> FT_Get_Name_Index(). Inserting print statements to trace those calls
> I find that FT_Get_Name_Index is called:
> 7 times for each character in a Tempo
> 5 times for each character in a Text Script
> ...
> 1 time for each notehead
> 5
31 matches
Mail list logo
