21 Aug
2014
21 Aug
'14
12:21 p.m.
On Thu, Aug 21, 2014 at 11:55 AM, Jean SIMARD <jean.simard(a)xwiki.com> wrote:
Something else about the solution 2.1. Is a code of 2
letters is user
friendly?
It maybe easy for people which are using latin characters as native ('fr'
for
French, 'en' for English are easy) but does Armenian people know that they
must
use 'hy' or Tibetan use 'bo'?
It's really a question, maybe they are and my remark is off topic.
It is common to use those abbreviation, see
http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:JOL_2014_247_R_0001
for examples, of course Brazilian Portuguese will need a bit more that 2
letters, we should not forget it. That said, we could also provide some
hints on mouse over. It is not perfect, since touch device does not benefit
it, but when you do not know, you can also just try and you will quickly
learn.
On Thu, Aug 21, 2014 at 12:10:32PM +0300, Ecaterina Moraru (Valica) wrote:
We are discussing any default skin with Localization - Multilinguage - Yes.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Jean SIMARD <jean.simard(a)xwiki.com>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO
On Thu, Aug 21, 2014 at 12:00 PM,
vincent(a)massol.net <vincent(a)massol.net
wrote:
>
>
>
>
> On 21 Aug 2014 at 10:57:36, Guillaume Louis-Marie Delhumeau (
> gdelhumeau@xwiki.com(mailto:gdelhumeau@xwiki.com)) wrote:
>
> > Hi
> >
> > 2014-08-21 9:58 GMT+02:00 Ecaterina Moraru (Valica) :
> >
> > > Hi,
> > >
> > > First of all we need to decide how prominent we want this
> functionality to
> > > be.
> > > I would make it more transparent, since theoretically you should
change
> > > your language preference just once
(in the Administration, and per
> user)
> > > and all the pages should be displayed according to that preference.
> This is
> > > not something that need to be highly visible and that you would
change
> > > every day.
> >
> >
> > It's not true on a public wiki (like Wikipedia).
>
> That’s a good point, we need to agree which skin we’re discussing.
AFAIK
> we’re discussing Flamingo which is NOT a
public web site skin. When we
do a
> public web site skin we would need to take
this into consideration
indeed.
If you don't want to use it with localization
you just don't activate the
functionality.
My remark was that when discussing individual functionality is easy to
want
to make each particular functionality pop. The
real question is: are the
language markers more important than the Last modified author? More
important than the last modified time? Are they the same? Should language
mark compete with the other action buttons in the content menu? etc.
Anyway the fix for these problems is a 'standard'. In enumeration mode
(2.1.x) the language markers were links and displayed accordingly
(2.1.2),
in select mode (2.2.x) they have a dropdown so
they could be displayed as
buttons (2.2.1).
Thanks,
Caty
>
> Thanks
> -Vincent
>
> > > IMO it's more important to be better displayed when you want to
> > > create a new translation, than when you read one.
> > >
> > > Regarding the flag to represent languages you can read this comment
> with
> > > additional information about why we wouldn't do it like that
> > >
> > >
>
http://jira.xwiki.org/browse/XWIKI-9512?focusedCommentId=77895&page=com…
> > >
> > > Thanks,
> > > Caty
> > >
> > >
> > > On Wed, Aug 20, 2014 at 9:37 PM, Denis Gervalle wrote:
> > >
> > > > Hi Cathy,
> > > >
> > > > 2.1.1 is the one I prefer, 2.1.2 is also good but the separation
> between
> > > > language should be more clear, and it is less easy to see the
active
> > > one. I
> > > > have no fear about the scaling issue, even heavily multilingual
site
> like
> > > > those of the European Commission use such enumeration without
issue.
> And
> > > as
> > > > Guillaume said, it is really rare to have more than a few
languages
> > > anyway.
> > > > Other proposal implies multiple click/touch for the same purpose,
> which
> > > is
> > > > bad IMO for content. It is also important to only display
effectively
> > > > available languages, but with
an enum, it could be also good to
have
> the
> > > > option to also display unavailable one greyed, so language keep
their
> > > > location on screen.
> > > >
> > > > Regarding the UI language, 1.1 is fine, but maybe a bit large.
Having
> > > only
> > > > initial in the bar would be better IMO. Having also a more fancy
> > > solution,
> > > > like what I have done with bluebird (see http://softec.lu),
could be
> > > nice
> > > > to have as well... or a easy way to customize it that way with an
> > > > extension.
> > > >
> > > > Thanks,
> > > >
> > > >
> > > >
> > > > On Mon, Aug 18, 2014 at 5:34 PM, Ecaterina Moraru (Valica) <
> > > > valicac(a)gmail.com> wrote:
> > > >
> > > > > Hi devs,
> > > > >
> > > > > We have http://jira.xwiki.org/browse/XWIKI-10745 (Improve the
> display
> > > of
> > > > > available languages in Flamingo) which is related to
> > > > > http://jira.xwiki.org/browse/XWIKI-6402 (Separate Interface
> language
> > > and
> > > > > page language settings)
> > > > >
> > > > > While in Flamingo we could just make the language links look
> better,
> > > > > without changing the functionality, for the future, the
separation
> is
> > > > > something we might want to tackle, that's why I've
created this
> > > proposal
> > > > > page
> > > > >
> > > > >
> > > >
> > >
>
http://design.xwiki.org/xwiki/bin/view/Proposal/InterfaceAndContentLanguage…
> > >
> > > I am interested in what you think about the variants.
> > >
> > > Thanks,
> > > Caty
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs