W3C home > Mailing lists > Public > www-international@w3.org > July to September 2010

RE: For review: Using <b> and <i> tags

From: CE Whitehead <cewcathar@hotmail.com>
Date: Mon, 19 Jul 2010 16:56:26 -0400
Message-ID: <SNT142-w63792C2305E98F83A1D6ADB3BF0@phx.gbl>
To: <gunnar@bittersmann.de>, <ishida@w3.org>
CC: <www-international@w3.org>

Hi!


Suppose that the text is translated into Japanese but some English terms are left intact and some of these terms in English must be italicized.  Since Foreign language styling is not considered the best option, the only option is to create two styling for two classes of i tags -- a pain.


But yes, you could have different classes of i tags in this case; that might work --if the class is somehow changed automatically during translation.  Otherwise going through the document and changing the tags individually after a translation would be a nuisance (and translators are not always web developers and vice versa).
 
Best,
 
--C. E. Whitehead
cewcathar@hotmail.com
 
> Date: Mon, 19 Jul 2010 18:05:00 +0200
> From: gunnar@bittersmann.de
> To: ishida@w3.org
> CC: www-international@w3.org
> Subject: Re: For review: Using <b> and <i> tags
> 
> Richard Ishida scripsit (2010-07-19 17:47+02:00):
> > For such a simple approach to work, however, you need the CSS to be able to refer to the specific elements that need to be changed. That means to differentiate between<i> used for document names and<i> used for foreign language idioms if their styling diverges or may diverge in the future. The way to do that is to use class attributes.
> > Is that clearer?
> 
> To me, it is clear (has been before). But Iím not relevant here. The 
> point is: Is it clear to all readers? That I doubt.
> 
> Regards,
> Gunnar
> 

 		 	   		  
Received on Monday, 19 July 2010 20:57:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 19 July 2010 20:57:00 GMT