Live data from Hacker News

Show HN: Blast.js separates text for typographic manipulation

julian.com

11–20 of 20 posts

Re: Show HN: Blast.js separates text for typographic manipulation

#11
post #10

Nice work. I'm also a fan of velocity.js (and I wrote liquid-fire to make it easier to use velocity in Ember apps). My top use case for something like blast is applying typographic rules that aren't possible with CSS. Like adding extra letter-spacing to strings of all caps, and rendering "AM" and "PM" in small caps. I do several of these things already on an ad-hoc basis.

I'm about to start using Ember, and I can't wait to dive into liquid-fire. Thank you so much for putting this together, Edward.

As for micro-typographic rules: You'll find that a simple way of accomplishing this is to use Blast's generateValueClass option.

Re: Show HN: Blast.js separates text for typographic manipulation

#12
post #4

Earlier quoted context omitted.

In case you're unaware: Font Bomb is a (gimmicky) solution for literally "blowing up" text. Blast.js, in comparison, is a robust text parser for real-world typographic manipulation.

We changed the title to the first sentence of the article, which makes this clearer.

I don't think Show HN titles should ever be changed. What was the original?

Re: Show HN: Blast.js separates text for typographic manipulation

#15
post #12
post #4

Earlier quoted context omitted.

We changed the title to the first sentence of the article, which makes this clearer.

I don't think Show HN titles should ever be changed. What was the original?

Show HN: Blast.js – Rip text apart in JavaScript [ Stripe OSS Grant ]

Re: Show HN: Blast.js separates text for typographic manipulation

#16

Nice work. However, in the example on the main page when you choose sentences it thinks that "Blast.js" is a sentence with the beginning of another. I think that you should ignore a dot if it's there to declare a file extension.

It's actually supposed to, but there's a bug. Thanks for pointing this out. Fixing now... Fixed.

Re: Show HN: Blast.js separates text for typographic manipulation

#17
Lettering.js recently merged some great accessibility code[1] that improves UX for screen readers by adding ARIA attributes. Each targeted element is given an aria-label with the original content, and each created span is marked with aria-hidden to avoid having the reader pause at every element. Would you consider implementing something similar for screen readers?

[1] https://github.com/davatron5000/Lettering.js/pull/51

Re: Show HN: Blast.js separates text for typographic manipulation

#18
post #17

Lettering.js recently merged some great accessibility code[1] that improves UX for screen readers by adding ARIA attributes. Each targeted element is given an aria-label with the original content, and each created span is marked with aria-hidden to avoid having the reader pause at every element. Would you consider implementing something similar for screen readers? [1] https://github.com/davatron5000/Lettering.js/pull…

Absolutely. Fantastic suggestion. It's on my to-do list now. Thank you.

Re: Show HN: Blast.js separates text for typographic manipulation

#19
post #17

Lettering.js recently merged some great accessibility code[1] that improves UX for screen readers by adding ARIA attributes. Each targeted element is given an aria-label with the original content, and each created span is marked with aria-hidden to avoid having the reader pause at every element. Would you consider implementing something similar for screen readers? [1] https://github.com/davatron5000/Lettering.js/pull…

Absolutely. Fantastic suggestion. It's on my to-do list now. Thank you.

Awesome. Great job by the way!

Re: Show HN: Blast.js separates text for typographic manipulation

#20
> 5. All Latin alphabet languages and UTF-8 characters are supported.

This claim really needs revising, only latin languages are supported, and the implementation doesn't use the Unicode boundary analysis algorithms. It certainly doesn't support the whole of Unicode as it first appears.

This is a nice effort but make it clear that it's Latin-only. Also, how well does it measure up to the Unicode UAX #29 grapheme/word/sentence break algorithms?

Post reply on HN