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 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 imagine that it could be used for interesting markup /
> highlighting (highlighting searched words, marking up grammar errors,
> auto-likifying, etc.). Perhaps this would defeat part of the point of this
> approach to an API.
> Erik
>
>
> On Mon, Jun 1, 2009 at 11:51 AM, Aaron Boodman <a...@chromium.org> wrote:
>
>>
>> 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 too. I thought about
>> factoring out the code that finds the blocks. There are other use
>> cases near there. But for actually modifying the text nodes -- no, I
>> can't think of any other use cases.
>>
>> - a
>>
>>
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
