Re: (X)HTML5

On Monday, 12. July 2010 11:51:49 [email protected] wrote:
> Milian Wolff
> I like your approach, really, very much, however:
> 
> (X)HTML5
> 1. (X)HTML5 - or HTML5 - has been appointed by W3C as the
> successor of XHTML (2.0) for all development further on.
> Forget about obsolete HTML and replace it by HTML5
> tags/elements/attributes.
> 
> Nowadays all browsers support these new elements, more or
> less, whith the exception of IE8. But soon coming IE9 will
> support html5 by 100%. Quanta+4 should be looking forward,
> not backward, and implement the new directions pointed out
> by W3C.
> 
> There is nothing wrong to get a version of XHTML/XML plugin,
> it will of course be useful, but (X)HTML5 is the future.
> Maybe define it (X)HTML5/XML plugin, or - similarly to your
> quote - with HTML5 (but not HTML or SGML) support? Quanta+4
> must of course support it, view
> http://w3schools.com/html5/default.asp

Yes, I second that. I'll make sure that working on HTML5 will work in Quanta 
4. But I won't sacrifce backwards compatibility too much, since as Niko 
pointed out, IE 6 & 7 is sadly still popular...

> CSS(3)
> 2. It is neither wrong to support CSS3! We are already using
> many of these wonderful new tools, view
> http://w3schools.com/w3c/w3c_css.asp
> http://www.css3.info/

Yeah, good point - should be added.

> Check also that new Quanta css editor/plugin give you lower
> case attributes according to XHTML/(X)HTML5. Now it gives
> you obsolete UPPERCASE, picking colors, for instance.

Can you elaborate on that? For me the CSS plugin always gives me lowercase 
attributes and named colors. #FFF is equal to #fff though and totally depends 
on the users preference.

> Indentation: Now I use XML Style, tried also Normal, but it
> gives me problems in the CSS editor, after copy/cut and
> pasting. To get back original indentation you must give an
> Undo ctrl+z  after Paste ctrl+v. Annoying. Or should I
> change indentation style in editor, but does not seem to
> change anything in old Quanta+?

XML style is definitely a really bad choice for working on _CSS_ - don't do 
that. Either use Normal or better yet, write a indent script for CSS. It's 
quite easy, just plain JavaScript.

See: http://docs.kde.org/stable/en/kdesdk/kate/advanced-editing-tools-
scripting.html

If you want to work on that, I can show you how to get started and how to 
write unit tests for the indentation scripts. (Note: the latter is really 
easy).

> UTF8
> 3. Check that the editor supports typing all characters and
> in all languages. Only utf8 supports all characters and must
> be default encoding. We designers wish to be able to type
> and read multilingual body texts with all characters
> readable.
> 
> Todays Quanta+ force you to insert text from other editors,
> if you like to read what you typed. Compare this mix of
> Russian and Swedish:
> 
> a) "Дорогая моя! Även med våra åäö ..."
> 
> b) "Дорогая
> моя! Även med våra
> åäö ..."
> from old Quanta+.
> 
> Which one do you prefer, if read and edit your typing of
> body text?

You are apparently not aware of the setting in Quanta 3 that disables the 
automatic transliteration to the UTF8 entities. Simply turn it off and it 
should work.

Kate supports a multitude of encodings and in the development for KDE 4.5, 
Christoph (Kate maintainer) spent a long time to fix a lot of outstanding 
issues in that regard. Meaning: This should just work™.

> Leif Hjerpe, web designer (not [yet alas] developer)
> Using Quanta+3.5.10 (OpenSuse release) in KDE-4.3.5 (today
> crippled, but still usable). Location Sweden

You should update to newest KDE asap ;-)

Bye
-- 
Milian Wolff
[email protected]
http://milianw.de

_______________________________________________
Quanta mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/quanta

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAkw7D38ACgkQDA6yEs0dE5MDKQCeOjP0Y0/4O9oPL/hOWt0pyJiN
ryMAoJRVrgcQRKmJHPz0xiy0P1GeqWXB
=avsK
-----END PGP SIGNATURE-----