View Single Post
Old 03-29-2016, 02:50 PM   #30
bookman156
Addict
bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.
 
Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
Quote:
Originally Posted by KevinH View Post
If you read the entire article at the link you posted it recommended using "i" with a class name of "foreignwords" to effectively convey the semantic meaning of why that class is used.

To me that approach is better than nothing but heavily prone to error. It would be much better to have an attribute similar to epub:type or aria:role that has a controlled vocabulary one of which whose terms means "just indicating a foreign word here" officially.
I don't know much about epub:type or aria:role to say one way or the other, I bow to your superior knowledge on that. But I don't see why using a class would ever be heavily prone to error, because the class is defined in the stylesheet, so where would the error come from? Am I missing something?
bookman156 is offline   Reply With Quote