The author od Rainbow Folder wrote me. He has finished the new version (v2 [1]) of the program and asked me if I want to translate it again. I've said I'm available. But I'm not going to do it hurrying: I'll finish it in 7-10 days. I prefer to not interrupt what I'm doing now with my pyg: I'm enough lazy by myself.
At the present time I provided a text-only version of almost all the pages available.
But I found one time again how twisted is the CSS standard. And I decided I'll call it CSSucks from now on.
I tryed to rewrite the kanji info page (get via kanjidic2 querying), so to exchange the fixed previous layout -- table based -- with a more versatile version based on div tags, or at least this was the intentions.
The result was a total failure. And after a couple of days I restored the previous layout. It's fixed but at least it's manageable.
I wonder who is the genious who decided to use "center" for the horizontal alignement ("text-align") and "middle" for the vertical one ("vertical-align"). There isn't possible conflict, since both kind of alignements are considered different properties.
Funny to see how the background positioning ("background-position"), that could in fact lead to possible conflicts since allows both vertical and horizontal alignement types togheter, uses without any problem "center" for both the values!
Another weird thing is why both Firefox and Opera (I don't even consider IE) refuse to display any border value on a row-of-table object.
The CSS(ucks) v2.1 specifications define the border properties as properties of ALL the objects.
Another not-so-clear thing is how to deal with tables that are rebuilt via stylesheet. It's possible to use any object as an table element. But since the table works only when all its 3 base elements are presents (body, row, cell), and that this specs let you define just one of these, the browser it's forced to recreate the missing parts as anonimous objects while rendering the page to get the table works.
But what if I decide to turn on a row-of-table object? Some properties are exclusive of the TABLE element ("border-spacing" e "border-collapse"). How can I then reach the "wrapped" table to fix these properties if it's "anonimous" (exactly!)?
And btw the selectors work just downwards: from containers to containment, not on both directions.
bleh.
Ok. stop.
But it makes me angry to see people who claim to solving problems with twisted stuff that actually creates more troubles than the ones it'd be supposed to solve! (Especially if I have to deal with it too!) >: (
Anyway at the present time I'm working to finish the browsing section of the kanji dictionary. I'm slow but I'm still going.
A tiny step per day, and one day I'll arrive...
In the meanwhile I took a little break and I've created a tileset for the DwarfFortress game using the charset of the commodore 64. I uploaded it on the wiki. [2]
Another user has fixed my edit. I didn't understand why he has decided to add a double size version of the picture, since to get a double res you would just need to write it into the init file (still talking about people who get their life complicated without reason. *COUGH* haem..). Anyway... I'm not going to loose sleep on it.
now I get back to my pyg.
y.
