12 Nov
2014
12 Nov
'14
11:22 a.m.
On 12 Nov 2014 at 11:14:50, Ecaterina Moraru (Valica)
(valicac@gmail.com(mailto:valicac@gmail.com)) wrote:
The thing is that if we do it with CSS, we just apply
a rule in the skin
and automatically we have all the translations fixed.
But our goal is not to capitalize all translations! It’s only to capitalize some (labels,
column labels, titles, etc).
With your solution we
would need to 'deprecate' lots of translations and just use the new format.
Is a lengthy process.
No we don’t deprecate anything, we just need to fix some translations.
If we do it from Translations, yes we can apply it
just for one language,
thing we cannot do with CSS, which applies the change globally.
It’s definitely -1 to for all languages since again each language has different
capitalization rules.
The problem with changing just English is that
according to Emanuel, all
the other languages will look 'less professional’.
That’s one of the worst possible reason I’ve ever heard ;)
Just for the record, in Colibri labels and buttons
were uppercase.
What? You mean someone changed the “Add comment” label translation (for example) from “Add
Comment” to “Add comment” when we switched to Flamingo? Are you really sure?
Thanks
-Vincent
Thanks,
Caty
On Wed, Nov 12, 2014 at 12:03 PM, vincent(a)massol.net
wrote:
> Hi Caty,
>
>
> On 12 Nov 2014 at 10:58:36, Ecaterina Moraru (Valica) (valicac(a)gmail.com
> (mailto:valicac@gmail.com)) wrote:
>
> > Should we do the capitalization from CSS or also when writing the
> > Translations?
> >
> > I would like it to be through CSS. This way if someone doesn't like it,
> can
> > create a custom skin and reset it: initial, uppercase, etc. Also note
> that
> > certain languages (german for example) have meaning problems capitalizing
> > all the words.
> >
> > In your example:
> > * “Reset to default” —> “Reset to Default”
> > this cannot be done with CSS. We either capitalize all the words or none,
> > we cannot skip one.
>
> I’d be -1 for CSS since:
>
> * extra CPU work not required
> * doesn’t work as you mentioned for “Reset to Default"
> * it’s not something optional that the user should be allowed to change!
> If they really want they’ll just need to override the translations (similar
> use case than if they wish to change some wording)
>
> Note that the rule I’m proposing is *ONLY* for English. I’m not proposing
> anything for other languages (each language has its own rules regarding
> Capitalization).
>
> Thanks
> -Vincent
>
>
> > Thanks,
> > Caty
> >
> >
> > On Wed, Nov 12, 2014 at 10:31 AM, Manuel Smeria wrote:
> >
> > > Hello,
> > >
> > > Here's my +1.
> > >
> > > I always thought capitalized buttons look more professional :)
> > >
> > > Thanks,
> > > Manuel
> > >
> > > On Wed, Nov 12, 2014 at 10:21 AM, vincent(a)massol.net
> > > wrote:
> > >
> > > > Hi devs,
> > > >
> > > > Andrea created an issue about capitalizing button labels (
> > > > http://jira.xwiki.org/browse/XWIKI-11265) and I think it’s a good
> idea
> > > > that we decide some rules about capitalization indeed.
> > > >
> > > > I’ve found this document from MSDN:
> > > >
> > > >
> > >
> http://msdn.microsoft.com/en-us/library/windows/desktop/bb246428(v=vs.85).a…
> > > >
> > > > I propose to adopt this document’s content as our rule for
> Capitalization
> > > > and to document that in our dev best practices on dev.xwiki.org.
> > > >
> > > > Example of labels:
> > > > * “Add comment” —> “Add Comment”
> > > > * “Reset to default” —> “Reset to Default”
> > > >
> > > > WDYT?
> > > >
> > > > Thanks
> > > > -Vincent