21 Aug
2014
21 Aug
'14
12:14 p.m.
On Thu, Aug 21, 2014 at 9:58 AM, Ecaterina Moraru (Valica) <
valicac(a)gmail.com> wrote:
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.
I do agree for the UI language, I absolutely not seing the content language
that way. In particular, collaboration on multilingual project really need
to easily change languages and see what is available at a glance.
IMO it's more important to be better displayed
when you want to
create a new translation, than when you read one.
For this kind of purpose, I would suggest to have a simplified language
management where UI and content language are more tightly linked in view
mode, and managed from a single choice using a 1.1 UI
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…
I know already about that, this is what I mean by fancy. It is not only a
matter of being rigorous here but also to provide flexibility, since it
depends on purposes. As I said, it should not be standard, but it should be
feasible through extensions.
Thanks,
Thanks,
Caty
On Wed, Aug 20, 2014 at 9:37 PM, Denis Gervalle <dgl(a)softec.lu> wrote:
http://design.xwiki.org/xwiki/bin/view/Proposal/InterfaceAndContentLanguage…
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO
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
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
--
Denis Gervalle
SOFTEC sa - CEO
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs