Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <1569130197-1358321312-cardhu_decombobulator_blackberry.rim.net-850294639-@b12.c8.bise7.blackberry>
References: <50E870C3.8020704@apache.org>
	<50E880C3.1080303@apache.org>
	<50EB3201.90400@wtnet.de>
	<CAP-ksojPRHCHic7Rz+SimZ5RYxi6VC04SfDwM+0++fStvSzMWw@mail.gmail.com>
	<50EB4046.7090200@wtnet.de>
	<50EC82FD.3090105@apache.org>
	<50EF3473.9000108@wtnet.de>
	<CAP-ksohqqLkwBjKeVg-TpLFVFFLcGkdH8G5bfyi6KKVEX3=bgQ@mail.gmail.com>
	<50EF3E1E.9030702@wtnet.de>
	<CAP-ksohvJD=+fARtQRb25UL9hdCpnbvf4J4STVXxGRKrpdFxmg@mail.gmail.com>
	<50F07601.8020205@wtnet.de>
	<CAP-ksojmMdK25g_mSBfTFc7+NaiwMESt0JPyp9cdkQNZ3PZ7Yg@mail.gmail.com>
	<50F30BCF.6050705@wtnet.de>
	<CAP-ksoj7E_007-nLr7+ezAtgA9wPTbJHQzcGBi2snPENmvUoNQ@mail.gmail.com>
	<50F3B14B.3070904@apache.org>
	<CAP-ksoiN=xAsq7k6-XCi3=tP_YRz5Q1-4TAR=gW_V9-i_ViyXg@mail.gmail.com>
	<CAP-ksojci57mOWWTZPsoFBp+AtNC6Qh8NLGFuMhPPe4B1JApHQ@mail.gmail.com>
	<690799816-1358268531-cardhu_decombobulator_blackberry.rim.net-648081495-@b12.c8.bise7.blackberry>
	<CAP-ksohZfPLa=RbS6U6bWGLYfepYvYpTFKQFQYom6Ysu6dko3g@mail.gmail.com>
	<50F5FAA3.9020303@apache.org>
	<1569130197-1358321312-cardhu_decombobulator_blackberry.rim.net-850294639-@b12.c8.bise7.blackberry>
Date: Wed, 16 Jan 2013 10:36:52 -0500
Message-ID: 
 <CAP-ksojWMf0fMRA6x9JGPfCGEwQUzVAR=Sj2DQbTaMn5h8g+nQ@mail.gmail.com>
Subject: Re: [WEBSITE] broken link on mac porting page
From: Rob Weir <robweir@apache.org>
To: dev@openoffice.apache.org, saransh@upscale.in
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 16, 2013 at 2:28 AM,  <saransh@upscale.in> wrote:
> Hey but bootstrap is not alone on js its on cuss too and you don't have t=
o make drastic changes
>
> Its simple enough to apply,


It may be worth prototyping what it could look like for some pages.
We have the ability, for example, to compare alternative versions of
the same page and see which one is better at achieving some measurable
goal, e.g., download conversion rate, time on page, abandon rate, etc.

But the main concern, I think, is that we don't get too far ahead of
the browser capabilities in use by our users.  But if we want a rough
estimate, here is what I see for % of visits for all browsers that
represent 1% or more of the visits:

1.	Chrome	23.0.1271.97	23.92%=09
2.	Firefox	17.0		18.19%
3.	Internet Explorer	9.0	13.56%
4.	Internet Explorer	8.0	8.70%
5.	Internet Explorer	10.0	4.48%
6.	Safari	536.26.17		3.89%
7.	Firefox	18.0	2.93%
8.	Chrome	24.0.1312.52	2.05%
9.	Firefox	16.0	1.63%
10.	Safari	534.57.2	1.59%
11.	Internet Explorer	7.0	1.51%
12.	Opera	12.12	1.29%
13.	Chrome	23.0.1271.101	1.26%

Note that together is only 85% of our visitors.  The "long tail" has
older versions.  With over 5 million website visitors/month, even
losing access for 1% means 50,000 users blocked.

-Rob

> Sent from BlackBerry=C2=AE on Airtel
>
> -----Original Message-----
> From: Andrea Pescetti <pescetti@apache.org>
> Date: Wed, 16 Jan 2013 01:56:03
> To: <dev@openoffice.apache.org>
> Reply-To: dev@openoffice.apache.org
> Subject: Re: [WEBSITE] broken link on mac porting page
>
> Rob Weir wrote:
>> On Tue, Jan 15, 2013 at 11:48 AM, saransh wrote:
>>> Can we make a website with automated language selector or optional
>>> language selector
>
> Sure, if you want to give it a try just provide somewhere a version of
> the index.html page with the additional selector and a working
> redirection to the native lang pages (example: German
> http://www.openoffice.org/de/ ; Italian http://www.openoffice.org/it );
> but read below for constraints.
>
>>> and over all I m not convinced really website
>>> looks great either you can incorporate bootstrap into it what do
>>> you say...
>> I'm not very familiar with Bootstrap.  Can you explain more?  For
>> example, does it require server-side processing?
>
> No, Bootstrap is a JavaScript framework under Apache License 2:
> http://twitter.github.com/bootstrap/ ; while very good for certain use
> cases, we probably don't want to depend on a JavaScript framework at the
> moment. So no jQuery, no Bootstrap, even though I wouldn't rule them out
> if we at a certain time restructure the whole site.
>
>> And for a language selector, we talked at one time about adding the
>> Google Translate drop down on each page, to make it easier for
>> visitors to get a page translated
>
> It would be enough to have a language selector on the homepage (or
> everywhere, but redirecting to the native-lang homepage). So, no content
> translation, but merely a redirection to a localized website. Now, to
> see the German site, one has to click on "Native Language" and then
> select "German". Having a language drop-down near the search box would
> improve the user experience. (By the way: no flags, language names are
> OK and politically correct).
>
> Regards,
>    Andrea.