RE: BP 24: what's all that about?

> > Yes, by 'markup as text' I mean things like "<p>This is a 
> > paragraph</p>"
...
> > How do you make the distinction between text and markup for 
> > translation, for spell-checking, etc.

Text surrounded by <...> is just content, not markup, so I think you
would handle it for translation, spell-checking etc in just the same way as
other content, wouldn't you?  ie, yes, if you wanted it not to be translated
you'd need an element around it to which to attach a no translate flag -
just as you would with any other content.

I still don't see why one would ban <...&gt.

RI

PS: We should check that we have surrounded any examples in the actual BP
doc with no translate flags.

============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)
 
http://www.w3.org/International/
http://rishida.net/blog/
http://rishida.net/

 
 

> -----Original Message-----
> From: Felix Sasaki [mailto:fsasaki@w3.org] 
> Sent: 05 December 2007 00:36
> To: Yves Savourel
> Cc: 'Richard Ishida'; public-i18n-its@w3.org
> Subject: RE: BP 24: what's all that about?
> 
> >
> > Hi Richard,
> >
> >> Your reply doesn't give me more than I can currently read in the 
> >> document.
> >> My problem is, I think, understanding what you mean by 
> 'markup as text'.
> >> By 'as text' do you mean, eg., examples like we have in 
> the BP document?
> >> What's wrong with <p>This is a paragraph</p> ?
> >
> > Yes, by 'markup as text' I mean things like "<p>This is a 
> > paragraph</p>"
> >
> > What is wrong with it? --> "<p>" and "</p>"
> >
> > How do you make the distinction between text and markup for 
> > translation, for spell-checking, etc.
> 
> to give an example from XPath: "//p" will not give you back 
> the content of "<p>"..."</p>" .
> 
> Felix
>

Received on Wednesday, 5 December 2007 12:06:55 UTC