New fonts

Love the Bebas Neue font for Headings.

Unfortunately it does not appear to render letters with diacritics (foreign accents) well. Specifically, French and German text. The font seems to revert to a wider type on letters that have an accent, which looks.... very odd.

I tried using the "insert special character" button in the text style editor. Same result.

I then tried using a different font, and the issue disappeared. Great. But... none of the other options have a bold-condensed-all-caps look, so the titles seem to merge with the body text, rather than stand out, and the impact is diluted down to blah. :(

Is there any way to check to see if that font (or an equivalent) comes with official diacritics? Or add a font color option to the Customize > Theme > Fonts > Headings Font ?

With regard to diacritics in Bebas Neue, please see this forum thread which should hopefully help in conjunction with the information in the Adding Custom Styles and Fonts section of the Showkase support pages.

Took me awhile to figure out the CSS and directory paths, but I got it sorted in the end.

New wrinkle.

The font appears to render correctly in the body of the page (http://174.122.127.226/~petraluz/DE/uuraaleet//) but not in the nav area. See the last button on the nav.
My custom.css file contains:

/* Generated by Font Squirrel (http://www.fontsquirrel.com) on January 23, 2013 10:16:30 PM America/New_York */

@font-face {
    font-family: 'BebasNeueRegular';
    src: url('../../../fonts/BebasNeue-webfont.eot');
    src: url('../../../fonts/BebasNeue-webfont.eot?#iefix') format('embedded-opentype'),
         url('../../../fonts/BebasNeue-webfont.woff') format('woff'),
         url('../../../fonts/BebasNeue-webfont.ttf') format('truetype'),
         url('../../../fonts/BebasNeue-webfont.svg#BebasNeueRegular') format('svg');
    font-weight: normal;
    font-style: normal;

}

header hgroup h1 {
  font-family: 'BebasNeueRegular', Arial, sans-serif;
  font-size: 18px;
  line-height: 1.5;
}

header hgroup {
  font-family: 'BebasNeueRegular', Arial, sans-serif;

}

Also, on Windows machines in IE 7 and 8, even after installing the Intnl French version of the font, the French accents are not rendering properly: http://174.122.127.226/~petraluz/FR/

Of course it all looks fine on my Mac (Safari 6.0.2, Chrome 24, Firefox 18.0.2). But try explaining that to a client using IE 7 or 8, who are convinced their demographic uses similar.

I think you should replace Bebas Neue. Seriously. It's a default font in Kosel, and the only condensed font option, so it's gonna cause umpteen headaches for anyone else even referencing a foreign text or name within an English site.

As I mentioned above, Google webfonts (http://www.google.com/webfonts) have a couple that are almost identical to Bebas Neue but have full diacritics:

Roboto Condensed Bold (700 weight)

BenchNine Bold (700 weight)

No, it seems to have a problem with the Ë in the body as well: http://174.122.127.226/~petraluz/DE/galerien/  (see the name of the first gallery).

At first I had the wrong fontkit loaded (French instead of German) and everything was fine except the Ä. Then I loaded the correct German fontkit and the problem switched to the Ë. This makes me suspect that they have carved up the diacritics according to each language for each language kit, rather than include all diacritics. Possibly to increase the speed of the page load. But this backfires when you have an English site that mentions, for example, both French and German authors/books/places/adopted phrases and you need both sets. I wish it was a full font, like the alternative font options in the theme, so that all letters would render properly. That, or replace Bebas Neue with another condensed-bold font that comes with a full set of diacritics.(If I didn't love the contrast of a bold-condensed font with plain ol' sans serif Arial, I'd have just chosen an alternative font from the theme options ages ago and spared myself this hassle. But the theme designer made a strong design choice when setting this as the default look for Kosel, and it really is the best pairing IMHO.)

I read the forum entry above and yes, I have already done that and just re-checked my code and it appears correct. I appreciate your forwarding the issue to the developers. The site is due to go live this week, so fingers crossed they address it asap.