There has been some discussion on the w3c/whatwg mailing lists about how
far we can mark up content with linguistic tags, such as marking word
and/or sentence boundaries.
In my authoring of web apps, I often write a short manual into a hidden
div, so that the vocabulary of my application can
On Wed, May 2, 2012 at 9:59 AM, Charles Pritchard ch...@jumis.com wrote:
There has been some discussion on the w3c/whatwg mailing lists about how far
we can mark up content with linguistic tags, such as marking word and/or
sentence boundaries.
In my authoring of web apps, I often write a
On 5/2/12 10:50 AM, Tab Atkins Jr. wrote:
On Wed, May 2, 2012 at 9:59 AM, Charles Pritchardch...@jumis.com wrote:
There has been some discussion on the w3c/whatwg mailing lists about how far
we can mark up content with linguistic tags, such as marking word and/or
sentence boundaries.
In my
On Wed, May 2, 2012 at 6:59 PM, Charles Pritchard ch...@jumis.com wrote:
If you do expect that, have you evaluated the existing mechanisms for
embedding custom data in the page and found them wanting? If so, how?
1. Google translate gets a little loose with some markup, to where the
On 5/2/12 11:46 AM, Benjamin Hawkes-Lewis wrote:
On Wed, May 2, 2012 at 6:59 PM, Charles Pritchardch...@jumis.com wrote:
If you do expect that, have you evaluated the existing mechanisms for
embedding custom data in the page and found them wanting? If so, how?
1. New features won't fix Google
On Wed, May 2, 2012 at 8:01 PM, Charles Pritchard ch...@jumis.com wrote:
1. New features won't fix Google Translate bugs with existing
features, and it's more efficient for Google to fix Translate than for
the community to design, specify, and implement new features.
New features do allow
On Thu, May 3, 2012 at 2:59 AM, Charles Pritchard ch...@jumis.com wrote:
There has been some discussion on the w3c/whatwg mailing lists about how far
we can mark up content with linguistic tags, such as marking word and/or
sentence boundaries.
In my authoring of web apps, I often write a
