Comments by Jed Schmidt

You might want to create your own original "feedback" image for the tab on the left. Yours[1] appears to have been copied from uservoice[2].

[1] http://www.fromabirdie.com/images/feedback_tab_white.png [2] http://cdn.uservoice.com/images/widgets/en/feedback_tab_white.png

Reply | Original | Permalink | Tweet

Check out the jQuery Metadata plugin:

http://plugins.jquery.com/project/metadata

It lets you choose where to define this kind of custom data: in an arbitrary attribute, as a class within the className attribute, or in a script tag.

Reply | Original | Permalink | Tweet

Yes, that is why it's not a translation, but a localization (you know, for the locals).

Reply | Original | Permalink | Tweet

It's a lesson in the difference between translation and localization.

In this case, Google's approach confuses the latter for the former, because its corpus contains parallel texts that have not only been translated (into a different language), but also localized (into a different locale). For example, it may be extrapolating incorrectly from a French document and an English document with the following phrases in the same location:

FR Cliquez ici pour la version anglaise. EN Click here for the French version.This sign is another good example of how parallel texts are not always translations:

http://flickr.com/photos/jadelin/2205088201/

(the Japanese "おかえりなさい" here means "Welcome home")

Reply | Original | Permalink | Tweet

It's a lesson in the difference between translation and localization.

In this case, Google's approach confuses the latter for the former, because its corpus contains parallel texts that have not only been translated (into a different language), but also localized (into a different locale). For example, it may be extrapolating incorrectly from a French document and an English document with the following phrases in the same location:

FR Click here for the English version. EN Click here for the French version.This sign is another good example of how parallel texts are not always translations:

http://flickr.com/photos/jadelin/2205088201/

(the Japanese "おかえりなさい" here means "Welcome home")

Reply | Original | Permalink | Tweet

Is this cheating?

http://www.google.com/search?q=00000000000000000000000000000...

Reply | Original | Permalink | Tweet

That's a good point. Fixed.

Reply | Original | Permalink | Tweet

I'm having trouble recreating this. What's your OS/browser?

Reply | Original | Permalink | Tweet

I agree. It's not monetizable in its current state, but I'm curious what features you think would get it closer, such as:

* more rich replacement (including functions/regex) * dynamic content like stock prices * ability to chain expansions quasi-recursively * SSL / privacy

As a reference point, TextExpander (http://www.smileonmymac.com/TextExpander/) is an OS X app that offers similar functionality, and it's $30.

Reply | Original | Permalink | Tweet

I agree. It's not monetizable in its current state, but I'm curious what features you think would get it closer, such as:

* more rich replacement (including functions/regex)* dynamic content like stock prices* ability to chain expansions quasi-recursively* SSL / privacy

As a reference point, TextExpander (http://www.smileonmymac.com/TextExpander/) is an OS X app that offers similar functionality, and it's $30.

Reply | Original | Permalink | Tweet

After getting such useful feedback on HN for typd.in this week (special thanks to huhtenberg/LogicHoleFlaw/ken), I thought I'd put our next project out there to get some more ideas.

textpanda is a simple bookmarklet that lets you define shortcuts for any text input on the web (think really simple emacs bindings). Since it's more of a quick proof of concept than anything, we're not quite sure what to add next (functions and other dynamic replacement? real user authentication? subscriptions to other users' macros?) and would love to hear what you guys think.

Reply | Original | Permalink | Tweet

Thanks for the good feedback. I think we'll need to move the indicator to the left side and pad the input to offset it, so that it's more visible.

Correcting scrolling is less trivial, and will have to wait for v2.

Reply | Original | Permalink | Tweet

One of the trade-offs of using an unobtrusive approach (no DOM insertion) to maximize compatibility is that we're limited to the decoration offered by a vanilla text control. Otherwise, the flow of insertion/deletion/selection was based on OS X, so I think you'll find it familiar.

Reply | Original | Permalink | Tweet

Technically, it's a misspelling for こんぴゅーたー (konpyu-ta-), which converts correctly into katakana.

But I really got a kick out of seeing someone use the tool itself to give us feedback...

Reply | Original | Permalink | Tweet

This is exactly what we had in mind. The latency of hitting the server for each kanji conversion would make it difficult to compete with a native implementation, but this is just a hack to fill in the holes when no such implementation exists.

Aside from other language support, we're thinking of eventually implementing a passive feedback mechanism that would tell the back end about conversion preferences, so that users could teach the system merely by correcting suggestions.

Reply | Original | Permalink | Tweet

1. « Previous
2. Page:
3. 1
4. 2
5. Next »