impallari / font-testing-page Goto Github PK

http://www.chromeexperiments.com/detail/responsive-typography-with-webrtc/

I've noticed toggling 'OpenType Kerning' doesn't turn on kerning in some fonts, it happens in Chrome 35.0.1916.153 with ttf, otf and woff versions (for example Roboto-Thin.ttf doesn't but CooperHewitt-Thin.otf, ClearSans-Regular.ttf works).

I know there is kerning in these fonts and when I tested it in another html page with text-rendering: optimizeLegibility the kerning works.

The Text paragraphs do not wrap long strings:

jQuery contentEditable() plugin is GPL 2.

As per EkType/Mukta#12, on Deva Syllables page, move 'impossible' combinations to their own row

https://github.com/jeremychurch/type-scale

#5 can be done as a jQuery iterator that adds the contentEditable attribute to all P tags after the page has loaded

Somehow we forgot to add FontDragr to the credits, shame on us! Fix asap

Next to the ssXX selectors, you could add 4 blank 4-letter text fields (two next to ss10 and two next to ss20), with checkboxes next to each. This way, I could enter custom 4-letter OpenType feature tags (e.g. "fina" or "hist" or "afrc" or "ornm" or "unic" etc.) and have them also easily applied to the samples. The checkboxes would work the same way as they already do.

The idea is to quickly compare two or more fonts and make diffs between shapes and spacing to pop out. For that I suggest to add keyboard focus on the fonts tabs. Then it could be nice to see top numerals 1,2,3,4,5 switch to the first, second, third… font tab.

Use http://nodebox.github.io/opentype.js/ to test if 2+ fonts are interpolatable

When you delete a row of text, sometimes a P tag can get deleted, so the contentEditable attributes should be on the P tags, not their parent DIV

Would be nice to not have to jump to the top to change features?

Rewrite the sentence generator from https://github.com/hash3g/example-trigram in javascript and use it to populate all test strings with sentences that only use input characters

from https://github.com/enathu/tamil-font-testing-page

The font stack should have the SIL UBF Font as the 2nd in the stack, so glyphs not present are visible.

http://typedrawers.com/discussion/50/drag-and-drop-font-testing-page#latest

@lemzwerg is adding support for a LOT of scripts to ttfautohint; I'd like him to contribute hint testing pages to this project (ie, font cascades for relevant sizes)

The Noto demo texts for the many scripts are available at https://github.com/googlei18n/nototools/tree/master/sample_texts and I suggest to use those as a start.

@impallari how can this be done in a way that you'll accept upstream? :)

Instead of having 2 fixed sizes (600px or 920px) make the width flexible. @impallari could you explain more? :)

This is an important feature that's missing as font weights are often used together and possibly on the same line, it's necessary to proof webfonts in a family together.

#55

Hi Pablo,

Please can you integrate Tamil testing. I am looking at the world scripts where there is Tamil, however a more elaborate testing interface will be very useful.

Thanks in advance.

Best,
Pria

When comparing 2 fonts of 2 families (eg Lohit Devanagari and Ek Mukta Regular on http://www.impallari.com/testing/devatest.php) then the baseline of each line jumps because the 2 fonts have different vertical metrics.

It would be great if there was an option so that the line-height of the page was fixed and that jump didn't happen, so when you toggle the 2 fonts, you can more easily compare the differences

Hello,

Now that both Chrome and Firefox (v35, via about:config) support woff2, it would be nice to be able to add support for the new format to the Font Testing Page.

For the time being, I simply rename the font file extension to, say, ".woff", and the WOFF2 is loaded correctly by supported browsers.

So I guess it's just a matter of adding the "woff2" extension to the fontdrag.js list of acceptedFileExtension...
(but maybe this feature request could also be forwarded to @ryanseddon's font-dragr repository)

Thanks a lot,

Cosimo

Use SASS for the css, with the OTL mixin from https://github.com/davelab6/otfeatures

Generally modernise the whole project as a JS tool :)

I wonder if you can use http://somadesign.ca/projects/fontfriend/ instead of fontDragr, so that system fonts and all Fonts API fonts are easy to add to the page....

On the "Latin" and "World Scipts" pages.

So that the missing characters get greyed out or become red or bold or

Don't know how to code this though.

I know you can use javascript (jsfiddle) or the unicode range in @font-face for styling but I'm not sure how to detect the missing glyphs.

http://vernnobile.github.io/webfont-testing has test strings to add to this :)

On the context-of-diacritics tests in the Latin 2 section, we have, for example "espanhóis" and "źródłosłowu" in the "ó" section. The first is Portuguese and the second is Polish. The Polish ó is a o-kreska which may be designed differently to o-acute; OpenType localisation features in the font can be used to select the appropriate glyph for a text.

For testing localised features, would it make sense to mark up all of the context-of-diacritics words in spans declaring their languages so the browser can at least have a shot at giving you the right glyph? For example, <span lang="pt">espanhóis</span> ... <span lang="pl">źródłosłowu</span> and so on.

Include ngrams from http://norvig.com/mayzner.html :)

If not needed, remove this line from README

http://codepen.io/TimPietrusky/pen/eHGfj (backup at https://gist.github.com/davelab6/6594172) could be one of the tabs ;)

Improve readme file.
Add documentation

Fonts with a number as the first char in the filename don't load, but they should :)

Update the Contributors list to include all the contributors of all the different versions.

http://typedrawers.com/discussion/comment/16373/#Comment_16373 mentions kerning tests for

(j
f)

Troush@2dbf4f9 seems missing from impallari.com/testing ..?

New improved layout will have:

• Dropped font list and OT Panel in the left sidebar
• Tabs Navigation at the Top

The way it works under the hood, it's a bit hard-coded, so lets make it more generic and customizable - so it will be easy to add more "specimen text"

http://www.impallari.com/testing/specimengenerator.php

A user told me,

I loaded my font into www.impallari.com/testing/, but unfortunately it was very difficult to view in isolation as the “default” font was still representing the missing glyphs that I have not worked on yet.

Using a non-system fallback font, like http://scripts.sil.org/UnicodeBMPFallbackFont

http://readableweb.com/tests/draganddrop/pangramdragndrop_ver8.1.zip

http://en.wikibooks.org/wiki/Hindi/Consonant_combinations

https://twitter.com/klimtypefoundry/status/616391429028380672

Hi,

There could an option to turn the css font smoothing on (font-smoothing: antialiased)

Don't You think?

Thanks.

@impallari I have done a sinhala iteration of tester. Can we add it to main tester?

Hi Pablo et al.,

it would be great if the testing page couldn't only use local files dragged into the header, but also webfonts at a given online location. Even better would be if that location could be specified as part of the URL calling the font testing page. This way, it could be used with BrowserStack to inspect a font on various platforms and in various browsers.

Cheers, Christian