Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-30 Thread Chusslove Illich
[: Stefan Majewsky :] I'm missing one point in this statistic: How big would the percentage be if KUIT was used in every relevant string? That is the main point of uncertainty. In here: http://lists.kde.org/?l=kde-core-develm=133258732919686w=2 I made the best estimate I could think of so

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-30 Thread Chusslove Illich
[: Albert Astals Cid :] Discipline is not a problem [...] [...] I agree optional is a bad idea. [...] OTOH it's another hurdle for adoption of current code from KDE 4 to KF5, that originally was said to be transparent for developers and each day is getting to look more like a bigger

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-27 Thread Stefan Majewsky
On Thu, Mar 22, 2012 at 11:25 AM, Chusslove Illich caslav.i...@gmx.net wrote: Only 0.56% of all messages (1144 out of 200,000) contain any [KUIT tags]. I'm missing one point in this statistic: How big would the percentage be if KUIT was used in every relevant string? I suspect that most

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-26 Thread Aurélien Gâteau
On Sat, 24 Mar 2012 12:06:25 +0100, Chusslove Illich wrote: [: Oswald Buddenhagen :] i would find this number way more helpful if it gave the percentage of strings with markup only amongst strings which have placeholders, as that is by far the most interesting target group. I recognize that

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-26 Thread Chusslove Illich
[: Aurélien Gâteau :] I would find it even more interesting (but probably more difficult/fuzzy to compute) to have the ratio of messages with KUIT markup over messages with Qt markup or using quotes. That excludes the cases which have no delimitation at all but could have some, which are not

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-24 Thread Chusslove Illich
[: Thomas Zander :] But can we be certain enough of succeeding now where we clearly failed before that this is actually worth stopping the innovations that Chusslove is working on? [: Albert Astals Cid :] I did not understand that it was stopping any innovation, Chusslove can you clarify

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-24 Thread Chusslove Illich
[: Oswald Buddenhagen :] i would find this number way more helpful if it gave the percentage of strings with markup only amongst strings which have placeholders, as that is by far the most interesting target group. I recognize that simply taking into account all messages is somewhat lacking,

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-24 Thread Allen Winter
On Friday 23 March 2012 9:17:43 AM Chusslove Illich wrote: [: Allen Winter :] Personally, I have put a lot of time and effort into adding KUIT into my projects over the years and think it is a great help, even if just for the developers to understand how the strings are being used. I

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-23 Thread Allen Winter
On Thursday 22 March 2012 6:25:36 AM Chusslove Illich wrote: Starting with KDE 4.0, i18n() functions act as XML processors under the hood, expecting the strings to be well-formed XML and resolving some tags (KUIT tags) to a target format (HTML or pure text). These KUIT tags include filename,

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-23 Thread David Jarvie
On Thu, March 22, 2012 5:47 pm, Chusslove Illich wrote: [: David Jarvie :] I understand from your email that you are only proposing to remove KUIT semantic tags, not KUIT context markers. Can you confirm this? I confirm. They are used much more than tags, and have no problems on their own;

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-23 Thread Chusslove Illich
[: David Jarvie :] The original intention of enabling consistent formatting of displayed text via semantic tags seems a very desirable one. Removing the tags seems to imply that KDE would abandon the aim of presenting a consistent interface for such items. If an inconsistent interface is

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-23 Thread Thomas Zander
On Friday 23 March 2012 19.39.26 Albert Astals Cid wrote: Removing the functional effects which context markers have, including the /format modifiers, might have a significant effect if this makes everything plain text rather than rich text, so at first sight I'm not too keen on this idea.

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-23 Thread Albert Astals Cid
El Divendres, 23 de març de 2012, a les 20:12:53, Thomas Zander va escriure: On Friday 23 March 2012 19.39.26 Albert Astals Cid wrote: Removing the functional effects which context markers have, including the /format modifiers, might have a significant effect if this makes everything

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-23 Thread Oswald Buddenhagen
On Fri, Mar 23, 2012 at 04:28:52PM +0100, Chusslove Illich wrote: It occured to me that I could examine usage-over-time statistics, since KDE 4.0. Here is the percentage of strings in core (SC) modules containing KUIT markup, [...] 2012-01-010.60% i would find this number way more

Re: Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-23 Thread Alex Fiestas
On Friday, March 23, 2012 08:12:53 PM Thomas Zander wrote: Read those numbers again; its kinda depressing really; I don't have numbers but almost nobody is taking close care of accessibility when developing applications, should be removed it? no we do not. I think that this feature, as Albert

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-22 Thread David Jarvie
On Thu, March 22, 2012 10:25 am, Chusslove Illich wrote: Starting with KDE 4.0, i18n() functions act as XML processors under the hood, expecting the strings to be well-formed XML and resolving some tags (KUIT tags) to a target format (HTML or pure text). These KUIT tags include filename,

Re: RFC: i18n: drop KUIT tags in KDE Frameworks 5.0?

2012-03-22 Thread Chusslove Illich
[: David Jarvie :] I understand from your email that you are only proposing to remove KUIT semantic tags, not KUIT context markers. Can you confirm this? I confirm. They are used much more than tags, and have no problems on their own; they are simply useful whenever present. They would only