Am 23.05.2016 um 09:01 schrieb Jacob Carlborg:
> On 2016-05-23 08:52, Sönke Ludwig wrote:
>
>> On which browser/OS?
>
> On OS X using Safari, Chrome or Firefox.
>
>> I've now removed the border/background color,
>
> I think the background and border looked fine.

It looked out of place on non-Mac systems. On OS X on the other hand, the monospace font is rendered hardly different from the serif one. I've added the border back, but lighter and with vertical padding, which looks okay on both systems.

>
>> but the font size looks fine for me on Linux.
>
> Using Firefox:
>
> The inline code has font size 15px. I think "Andale Mono" is the font
> that is actually used.
>
> For the code blocks, the font size is 13px and the font is "Courier New".
>
> The rest of the text is using "Roboto Slab" and 15px.
>

Okay, removed the old "Courier New" reference and both are rendered the same now.

On Monday, 23 May 2016 at 08:04:51 UTC, Sönke Ludwig wrote:
> Am 23.05.2016 um 09:01 schrieb Jacob Carlborg:
>> On 2016-05-23 08:52, Sönke Ludwig wrote:
>>
>>> On which browser/OS?
>>
>> On OS X using Safari, Chrome or Firefox.
>>
>>> I've now removed the border/background color,
>>
>> I think the background and border looked fine.
>
> It looked out of place on non-Mac systems. On OS X on the other hand, the monospace font is rendered hardly different from the serif one. I've added the border back, but lighter and with vertical padding, which looks okay on both systems.
>
>>
>>> but the font size looks fine for me on Linux.
>>
>> Using Firefox:
>>
>> The inline code has font size 15px. I think "Andale Mono" is the font
>> that is actually used.
>>
>> For the code blocks, the font size is 13px and the font is "Courier New".
>>
>> The rest of the text is using "Roboto Slab" and 15px.
>>
>
> Okay, removed the old "Courier New" reference and both are rendered the same now.

The flavicon is still the old one and appears in search engine results.

Am 23.05.2016 um 11:22 schrieb Chris:
> The flavicon is still the old one and appears in search engine results.

For some reason, favicons are cached aggressively. It has been updated, but it's hard to get the browsers pick it up.

On Monday, 23 May 2016 at 09:23:45 UTC, Sönke Ludwig wrote:
> Am 23.05.2016 um 11:22 schrieb Chris:
>> The flavicon is still the old one and appears in search engine results.
>
> For some reason, favicons are cached aggressively. It has been updated, but it's hard to get the browsers pick it up.

I thought it might be a caching issue. I don't know about the search engines though. Can you inform them of the update? I opened the page in a different browser and it shows the new favicon, but in the search results it's still the old icon.

On Monday, 23 May 2016 at 06:33:15 UTC, Jacob Carlborg wrote:
> The styling of [1] is a bit inconsistent. The styling for inline code, i.e. <code>, seem to have bigger font than both the regular text and the larger code blocks, <pre class="code">.
>
> [1] http://code.dlang.org/package-format?lang=json

Mixing fonts is hard. Both fonts must have the same size, but also the same x-height [0], which is the height of lowercase letters like x. This can be seen very clearly with inline code like "contain a <code>dub.json</code>" at the page you linked to. Zoom in (Ctrl+) and you see the height difference between "a" and "u".

On websites where fonts are picked from whatever is available on the system, this is nearly impossible to get right. You either live with it or embed your own fonts via CSS, which bloats the page.

[0] https://en.wikipedia.org/wiki/X-height

Am 23.05.2016 um 11:30 schrieb Chris:
> On Monday, 23 May 2016 at 09:23:45 UTC, Sönke Ludwig wrote:
>> Am 23.05.2016 um 11:22 schrieb Chris:
>>> The flavicon is still the old one and appears in search engine results.
>>
>> For some reason, favicons are cached aggressively. It has been
>> updated, but it's hard to get the browsers pick it up.
>
> I thought it might be a caching issue. I don't know about the search
> engines though. Can you inform them of the update? I opened the page in
> a different browser and it shows the new favicon, but in the search
> results it's still the old icon.

I'd hope that that would be part of the usual refresh cycle. At least I've never seen an option related to this.

Hi,

Is the Dub API published anywhere. I propose to write a dmd/ldc/gdc subtool so that dependency management based on the Dub repository is provided for SCons D builds.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Is there an ordering to the entries on the page?

Apologies if the ordering algorithm is obvious, I am having a relative brain-dead day today.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Am 23.05.2016 um 15:02 schrieb Russel Winder via Digitalmars-d-announce:
> Is there an ordering to the entries on the page?
>
> Apologies if the ordering algorithm is obvious, I am having a relative
> brain-dead day today.
>

You can click the column headers at the top. The default ordering is by latest update (latest tagged version).

Am 23.05.2016 um 15:01 schrieb Russel Winder via Digitalmars-d-announce:
> Hi,
>
> Is the Dub API published anywhere. I propose to write a dmd/ldc/gdc
> subtool so that dependency management based on the Dub repository is
> provided for SCons D builds.
>

Online docs are still on the TODO list, but you can do

    dub fetch dub
    dub run dub -b ddox

And it will start up a local HTTP server on http://127.0.0.1:8080/ with the API documentation.