Quote:
Originally Posted by BetterRed
A class based solution would be better, pity one can't put language code in CSS
|
Yeah, that is part of the reason why I created my own class called "greek' which I also apply. So I can just easily find it (and treat it differently) if needed.
As I said, those are easy as pie since they might need a different font (and you can easily tell just from the characters that are used).
Quote:
Originally Posted by BetterRed
I do it for free for me, family and friends, I try to avoid changing the code as much as possible - often all I do is spell check, as long as it readable on a couple of kindles & android tablets that's all I need. I don't care much about whether the code is pretty, elegant, efficient, whatever.
|
Even if you will be the only one seeing it, still good practice to follow some standards. Same with coding a little program for yourself, sure, you might be the only one looking at it, but you never know what might happen in the future (or writing comments/clean code for your future "self" (many times you look back at old code and think "who wrote this crap?" or "What the hell was I thinking?")).
Quote:
Originally Posted by BetterRed
Mainly because where does one stop. If I'm going to mark up Middle English quotes in a book written by a Pommie, then I should mark up Alyawarr quotes in a book written by an Aussie  |
One span at a time... One span at a time... 1 correctly marked language span is better than 0. 2 is better than 1, 3 is better than 2...
