Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Jasper de Waard

About

Username
Jasper de Waard
Joined
Visits
2,477
Last Active
Roles
Member
Points
146
Posts
227
  • Re: Separate language codes for different Englishes

    Quote mark standards, opening and nested

    „Afrikaans, Dutch, Polish”
         ‚Afrikaans, Dutch, Polish’

    „Bulgarian, Czech, German, Icelandic, Lithuanian, Slovak, Serbian, Romanian“
         ‚Bulgarian, Czech, German, Icelandic, Lithuanian, Slovak, Serbian, Romanian‘

    »Danish, Croatian«
         ›Danish, Croatian‹

    «Greek, Spanish, Albanian, Switzerland, Turkish»
         ‹Greek, Spanish, Albanian, Switzerland, Turkish›

    ‘British’
         “British”

    “American English, Irish, Portuguese”
         ‘American English, Irish, Portuguese’

    ”Finnish, Swedish”
         ’Finnish, Swedish’

    «French»
         “French” or ‹French›

    «Norwegian»
         ‘Norwegian’

    ***



    I would classify the use of quotes in the abovr scheme in Dutch as old fashioned, most current Dutch media would opt for the 'English' version, and both are correct. My point: these things are subject to fashion, so perhaps ill-suited to code into a typeface.

  • Re: Two more cases against pirates

    Not that I would advocate this kind of behavior, but it looks as if including a strange clause in the EULA and then sueing could be more profitable than selling 'normally'. That's really something to be avoided, and the only option I see is greater transparancy and simplicity in EULAs, across the whole market. Standardized EULAs, such as Fontspring offers (I believe?), can avoid the kind of distrust typeface designers may suffer, when/if sueing for an income becomes normalized.
  • Re: Dutch IJ with dots

    @John Savard
    Now there's an interesting hypothesis. Complexity of spelling's correlation with social inequality. Question is: how could we ever establish what is consequence and what is cause?


    Regarding the fij-problem:
    I may be able to speak for the younger generation. An fi ligature followed by a j, as in fijn, does look a little awkward. However, in many typefaces an unligated fi sequence will also look awkward, so the choice is one of two evils. Personally, I would opt for the ligature, since it stands out less than the excess whitespace that may be caused by an unligated fi. The best option (for this particular problem) remains an f that doesn't require a ligature. One could make such an f to be used only in the fij instance, but I suspect that would look awkward again.
  • Re: 2017 Font Purchasing Habits Survey Results (worth the read!)

    49% of people say they have read an entire EULA before

    Some of them may be lying, but I think this reveals a bigger issue about this survey: it's results are not representative for the total group of font-buyers. Respondents were often friends of typedesigners, I believe.
  • Re: Best Foundry Sites

    @Mike Wenzloff
    Why people say they buy things, and why they actually buy things, are two completely different things. Choices like purchases are usually largely driven by unconscious emotional stimuli, only to be rationalized (consciously) after the choice has already been made.

    So besides the obvious functionality reasons for having a good website, it should come as no surprise that a good website will reflect on the perceived quality of the typefaces (known as the halo effect).

    What would interest me A LOT are the conversion rates between different foundry websites.

    I myself don't have the time to give my website a much-needed overhaul at the moment.

    On my personal taste: Klim.co.nz hasn't been mentioned yet. Monokrom.no is also a beauty. When it comes to type foundries, I'm a sucker for websites that are largely in black and white.