Semantic tags for i18n, official proposal

[Allen Winter]

On Sunday 17 June 2007 10:26:54 am Chusslove Illich wrote:
> I have almost fully implemented the semantic markup for use in i18n
> messages, the KUIT (KDE UI Text), and it stands ready to commit. As base for
> comments, here is the article on Techbase:
> 
> http://techbase.kde.org/Development/Tutorials/Localization/i18n_Semantics
> 
> Any thoughts and proposals for modifications from the programmers,
> translators, and usability people (in alphabetic order :) are welcomed. The
> topic has already been somewhat discussed on kde-i18n-doc, kde-core-devel,
> and kde-usability, but I don't want to send you off to those threads, better
> to start fresh from the given proposal.
> 
> Some questions past the obvious:
> 
> What should the tag names look like? I've based them loosely on the Docbook,
> but they are not the Docbook. Especially I wanted to avoid any similarity
> with HTML, both for technical reasons (for the parser to differ them if
> combined) and for distinctiveness to programmers and translators.

I like the idea of re-using tag names we are familiar with.  Docbook is fine.
(texinfo would be fine too :>)

> 
> What other text modifications can you think of (like native separators in
> filepaths, or shortcut key separators)?

Really not sure until I start using it.  I'm sure we'll need more as time goes on.

> What should be the policy of using KUIT for new applications? Advise it
> strongly, just would-be-nice, or at-your-discretion?
> 
> What should be the policy of using KUIT in existing applications? Encourage
> programmers to update the messages as they see fit? To only to use KUIT in
> new messages and those which are changed due to some other reason? Or not to
> use it all?
> 
I think we start slow.  Encourage its use.
Provide tools to help migrate, as we discussed on #kde4-devel yesterday.
If we start seeing widespread use, then require it.  Make krazy complain
where semantic messages aren't used.

First thing that would help me is a tool showing where I'm not using
semantic messages, and suggestions on how to use them.

For example, a tool that would say 
 on line X use "@info, <title>List of Available Protocols</title>" instead of
"<h1>List of Available Protocols</h1>"... something like that.

Sorta like Frerich's docbook sanitizer on the EBN does things.

-Allen