Why not just rename textTranslate to textProcess or something in that
fashion. This feature could be used in other services rather than
translation.
-- Mohamed Mansour
On Mon, Jun 1, 2009 at 3:00 PM, Erik Kay erik...@chromium.org wrote:
Similar to the translate, this feature could be used to
This feels kinda one-off-y to me. Is there any use of this *other*
than running through Google Translate? I worry about adding a lot of
API surface area for little gain.
On Mon, Jun 1, 2009 at 11:29 AM, Aaron Boodman a...@chromium.org wrote:
Some people have expressed interest in
On Mon, Jun 1, 2009 at 11:46 AM, Evan Martin e...@chromium.org wrote:
This feels kinda one-off-y to me. Is there any use of this *other*
than running through Google Translate? I worry about adding a lot of
API surface area for little gain.
That is one of the things I was concerned about
Similar to the translate, this feature could be used to support sites that
use non-standard character set / font combinations (some indic websites
depend on downloadable fonts and custom character sets).
Also, if the API allowed styling of the text as opposed to just replacing
it, then I could
On Jun 1, 2009, at 12:00 PM, Erik Kay wrote:
Similar to the translate, this feature could be used to support
sites that use non-standard character set / font combinations (some
indic websites depend on downloadable fonts and custom character
sets).
Also, if the API allowed styling of
I understand the proposal, and am suggesting that having content
scripts might be a saner thing to do if they need to do less custom
stuff to get the job done. The API that locates the stuff could be
separate, but the transformation code feels like a natural content-
script task and one
