Confirmed.  However, we are at 2.0.1 now.

Hang about, this is a P1.

To quote the documentation:

P1 marks extremely severe problems.

There's rarely anything which really qualifies as P1 issue!
---
For more info please press the "Priority" link next to the priority selection 
list box.

Setting to P4 as this refers to an old version which has now been replaced 
with 2.0.1
Changing to "task".
I'm leving as confirmed as some people may want to download an older version 
than is current.  It also looks like there are 2.0.1 binaries at the 
oootranslation link.

There should be 2.0.1 binaries and 2.0.2 when it is released shortly. The en-GB
translation is completely up-to-date and AFAIK all relevant updates have been
submitted as required.

Thanks

I've made a post to the releases list.  Hopefully someone will have a look at 
this issue shortly.

Nobody has, so I've tried the distro-dev list.

While I may get shouted at for this, I'm reassigning to st.  I think he deals
with the download pages.

Greetings, We would be glad to see the page located at
http://l10n.openoffice.org/download/en-GB.html
We can provide a template and guide you through the initial setup.
Dan, Alex, could you maintain the page then?
Thanks, Stefan

I would be happy to point to a well maintained page. Please understand that I
have to close the issue as WONTFIX otherwise.

Wow there hold on!

Are you saying that you folk are not prepared to add en-GB to the list of
languanges for downloading?

Steady on, we have a localisation team that has gone to the trouble of
localising the product and you are not willing to provide a download link?

How do other languages get added to the download page?

If all you need is someone to maintain a page of HTML I'm sure we could find
someone within the localisation team - but remember we are a localisation team
not a web maintenance team.

Please don't close this as WONTFIX!!!!

David.

Hi again,

I was acting as a member of the qa team for this issue.  I don't have any 
links with the en-GB team, apart from being British myself.

I think what Stefan is suggesting is a special English download page for 
British English, but what David has requested is the British English version 
to be added to the current download pages at 
http://download.openoffice.org/2.0.1/index.html. 

It is important to point out here that British can understand American English 
(and Americans can understand British English), but people choose the British 
version out of preference.  I.e. color --> colour.  This means that a special 
download page *just* for British English is not required on the grounds 
of "people will not be able to download as they can't understand the standard 
(http://download.openoffice.org/2.0.1/index.html) download page".
However, if a special page is required by policy to get the en-GB version on 
the http://download.openoffice.org/2.0.1/index.html download page, or it would 
just make things easier in the long run, then this should be done.

If someone is required to maintain a special British English download page, 
then I would volunteer to help maintain it, if this is the only way to get it 
listed properly, although as mentioned before I am not (currently) a member of 
the British English internationalisation team.

May I also make the separate suggestion that the British English version be 
added to the standard mirror network, to make things easier, and at least get 
it on three UK mirrors.  However if this is a separate issue, then it should 
be filed as such.

Thanks.

If I go to www.openoffice.org there is nice big green button "download
OpenOffice.org". If I click this button I am taken to a generic download page on
which I can select which language and OS I want to download. Selecting a
language (or English and platform) takes me to a second generic download page.
This second page is identical for all languages I tried. At the bottom of this
page is a button that says "download".

If I click this button and I've selected English the download starts
immediately. If I have selected a different language then I am taken to the
localisation page.

Surely the correct thing is that if I've selected en-GB or en-US (or other
flavours of English in the future) when I click "download", the relevant version
should immediately start downloading exactly as for en-US. I see no need for
another page in between! I see no need to treat en-US and en-GB any differently.

Surely this is not a problem?

Obviously the en-GB version needs to be on the mirrors. We have advised the
releases team of its availability (months ago). I'm only involved in
localisation so I don't understand the details of how releases move through the
system into distribution. All I know is that we announced its availability along
with OOo 2.0 beta and it is still not yet available through the web site.

As skoorb mentioned en-GB is chosen by people out of preference. This is
particularly important as OOo moves into trials in UK schools, and it is also
important to some international organisations trialling alternatives to MSOffice
(they use British English as standard).

David.

uhm. actually the point is to create a space listing brit english (or whatever language lacking a NLC 
project) that, say, you, would maintain.  Right now, we have a set of more or less orphaned languages, 
that is languages without projects. These may not actually benefit from having a project but would from 
having a website destination. One example is British English; another could be Canadian (I live in Canada). 
Another is Swedish. Swedish does have an NLC, but it is not really maintained. Other languages could be 
the Southern African ones. As to being on the mirrors, I'm for it, but then we have to make sure that only 
qualified releases/builds make it there, yes?  

Does this clarify things?

louis

Sorry, what is an NLC?

Actually British English is neither orphaned nor unmaintained. In fact it is
actively being maintained and we have current milestone builds available and
up-to-date with all GUI, help, extras and other bits translated.

I personally put the 2.0 beta en-GB build through the QA process and we can
repeat that for any subsequent releases.

Some time ago I took a poll of the contributors and reviewers to see whether we
wanted a separate set of national language web pages - the answer was "It's not
necessary given that the main web site is in English."

So, what is the problem? Are you telling me that we *have* to register a
national language project before you will consider it? If so fine we'll do it,
but we felt it unecessary for the reasons above.

So given that en-GB *is* fully up-to-date and actively maintained what's the
problem?

David.

Dwayne, NLC is the Native Language Confederation. You know, the group we've been asking you to form a 
project with? :-)

You are also misreading what I write, alas.  I meant that the OOo *webpage* is not maintained. This will 
give you the ability to so maintain it. I am hardly suggesting that the  *build* is not maintained.  

Is that clearer? We are not interested in making your life (or anyone's) more difficult. The opposite. I am 
interested in particular in ensuring that webpages on OOo are adequately maintained....

louis

Louis, the comments were written by me, David - en-GB project lead, and not Dwayne.

Back to the point: Would someone please pick up this issue and add en-GB to the
download page and links?

Thanks
David.

David, please have a look how the form works for languages like German, French,
...  For those locales the form does not refer to installation files but to a
page speficic for the locale. We like to take the same approach for en-GB and
add an entry "English (GB)" that guides the user to a download page at
http://l10n.openoffice.org/download/en-GB.html

I think in terms of release maintenance en-GB is closer to these languages then
to en-US. A description about the steps to publish a localized builds is at
http://qa.openoffice.org/localized/
Please point to the builds that have been tested in a separate issue.

The website project is working to improve the download pages. For now I would
recommend we go ahead and

a) create a template download page for en-GB in the l10n project
b) guide dwb and/or skoorb through th epreparation for the page maintenance
c) publish the en-GB build to the mirror network
d) update the en-GB download page
e) add English (GB) to the list of languages on the global download page

Please indicate whether this would for you.

Thanks to you and your localisation team for taking care of en-GB.
Stefan

Stefan,

Thank you for you positive and constructive response - it is greatly
appreciated. I am happy to go with what you suggest and am willing to help out
where possible.

If you prefer to handle en-GB like the other languages: German, Dutch etc., that
will be fine. 

I'd really appreciate it if skoorb is prepared to help maintain the web page for
en-GB so that my focus is not drawn away from the localisation task too much.

Release 2.0.2 will be fully QA'd. We are familiar with the process having run
through the it for the milestone build at the 2.0beta stage.

Please just instruct me what I need to do next; If we could have it up and live
by the time 2.0.2 hits the servers we'll be happy.
Thanks a lot
David.

Sounds good; although I'm not an expert at web design, only a lowly computer 
science student, I’ll try to help.

Alex

I took care of a) and create the page template.

Alex, please have a look at the documentation about the needed setup for page
editing - ssh2 and cvs.
http://www.openoffice.org/scdocs/ddSSHGuide#thisguide
You could send questions to dev@native-lang.openoffice.org or come back to this
issue. We all went through this :-)

David, would you read over the QA process for localized builds please.
http://qa.openoffice.org/localized/index.html
The group handling the releases of localized builds is listening at
dev@qa.openoffice.org. Or come back to this issue...

I have added my public key to issue 61748.  I hope I have done this right.  If 
someone could do the necessary authorization, as the documentation mentioned my 
project lead needs to give authorization for me to be added.  Also, I'm not 
sure where I stand on the JCA front, perhaps someone could advise.

Thanks.

Just to confirm; I can log in to CVS successfully.

Could someone point me towards some documentation for point b: "guide dwb 
and/or skoorb through the preparation for the page maintenance"

I have a feeling there will be a relevant web page somewhere. :)

Thanks again

The page
 http://l10n.openoffice.org/download/en-GB.html
can be changed via modification of the CVS file
 l10n/www/download/en-GB.html

So you might want to 
 cvs co l10n/www/download/en-GB.html
then change and commit with
 cvs commit

Hi Alex, have you had a chance to play with CVS?

Oh Sorry, I had completely forgotten to respond… even though I had done a page.

There is a currently working download page at 
http://l10n.openoffice.org/download/en-GB.html.  At the moment it only points 
to one mirror (ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/680/), 
because this is the only one with the full install sets that I could find.

If I have made any mistakes, or missed any packages out, feel free to either 
let me know, or just correct the page.
Thanks

Please do not make ftp.linux.cz.../devel official URL.

You should QA the build and ask st to download it from there, but never point
final users there. This is development area and I will remove old milestones
once the final 2.0.2 is released...

The title of your page contains "SV".

Page looks fine apart from the title.

2.0 rc1 was put through the QA process and we advised the releases and l10n
lists of the results. 2.0.2 will once again be put through the QA process, the
work is under way at the moment, the only trouble is we don't actually know
which particular build we should be QA'ing - could someone please advise?

Thanks
David.

Whoops, I diddn't see the SV.  I don't have access to the machine with my ssh 
key on it atm.  I'll fix it when I get home this evening if I can (6pm or 
later GMT).

Please point me to somewhere where it can be downloaded from, as it isn't on 
the main mirror network.  I checked against the Tier 1 server: 
http://mirrors.dotsrc.org/openoffice/.  
http://mirrors.dotsrc.org/openoffice/localized/en-GB/ is empty.
I also checked oootranslation.services.openoffice.org.  No install sets there 
either.

Thanks

Page looks fine apart from the title.

2.0 rc1 was put through the QA process and we advised the releases and l10n
lists of the results. 2.0.2 will once again be put through the QA process, the
work is under way at the moment, the only trouble is we don't actually know
which particular build we should be QA'ing - could someone please advise?

Thanks
David.

Sorry for the last entry - hit go too soon.

The language packs for en_GB are available from:
http://oootranslation.services.openoffice.org/pub/OpenOffice.org/

So far I think only Pavel has built full installation sets for en_GB, though I
may be wrong.

O.K. then.  The download page now only points to the oootranslation lang packs.
I also put a big message saying that they are only langpacks.

We have now completed the QA tests for the Linux version and all tests passed
with the exception of saving files in the SW 3.0, SW 4.0 and SW 5.0 formats. For
these tests OOo crashed. This problem has been present in all Linux versions
that we've tested (including en-US) to date so I don't know whether it is a
known bug.

The version tested was 2.0.2 m5 (RC4 I believe) using the en-US build and the
en-GB language pack since a binary build for en-GB does not exist at this stage.
It was tested on both Fedora Core 1 and Gentoo systems. Testing of the Windows
version under Windows 2000 is under way at present and should be complete today.

Can we now have a binary build for en-GB please? How is distribution to the
mirrors arranged? It would be really good to have this done at the same time as
2.0.2 is released since we have completed the translation work and been through
the full suite of QA tests?

Thanks
David.

Testing of the Windows build for 680m5 under Windows NT 2k has been completed
now with no regressions found. It is considered fit for release. The builds used
are from here:
ftp://ftp.linux.cz/pub/localization/OpenOffice.org/devel/680/OOB680_m5/

Alex,

With a bit of luck en-GB builds should now be available on the mirrors (for
2.0.2). Could you please update the download page appropriately?

Thanks
David.

I checked:
ftp://mirrors.dotsrc.org/openoffice/localized/en-GB
ftp://ftp.gwdg.de/pub/misc/openoffice/localized/en-GB
ftp://ftp.stardiv.de/pub/OpenOffice.org/localized/en-GB
ftp://ftp.uni-muenster.de/pub/mirrors/ftp.openoffice.org/localized/en-GB
ftp://sunsite.informatik.rwth-aachen.de/pub/mirror/OpenOffice/localized/en-GB
and
ftp://ftp.snt.utwente.nl/pub/software/openoffice/localized/en-GB

There is still nothing there...
There are a few langpacks at
http://oootranslation.services.openoffice.org/pub/OpenOffice.org/2.0.2rc4/
though.

I will keep checking.

The full installation sets QA'ed according to issue 62891
are now propagating to the mirrors...

I have a working download page ready for 2.0.2, but when I try to use cvs, I am
getting a "/cvs: no such repository" error.  Have I missed a recent change?  As
far as I know, I havn't changed any cvs settings here.

So :pserver:skoorb@localhost:/cvs isn't working as my CVSROOT.

I'm not an expert at CVS, but I can't see anything wrong with the above, could
someone tell me what my CVSROOT should be?
I have no problems creating the ssh tunnel, that is established before I try CVS.

Thanks

Created attachment 35366 [details]
The en-GB download webpage updated for 2.0.2

skoorb: can you open a new issue for your cvs issues? assign to me or ST, www/www/general website 
issues

btw, the site will be down later on today starting at 01:00 UTC.

Cheers
Louis

The en-GB download page has been up for a bit now.  
I hope it is OK.
I avoided posting a comment as soon as it went up, as I was hoping to get all my
obscure CVS problems sorted first; I now have Cygwin working, but not Tortoise.
 I was unable to add comments to the files, as CVS kept complaining that VIM was
not installed, even though it was.  I think I have a solution now though.
Please let me know if you find anything wrong.
Thanks

en-GB builds are now appearing (since 3.1.1) on the download page as they pass 
QA (currently true for language packs, hopefully full install sets in future)

en-GB builds (installset & langpack) are now appearing on the download page as
they pass QA.

Can we close this issue now as FIXED?

Cheers

Stuart Swales (OOo en-GB lead)

@sswales: yes, if you think the original issue is fixed and nothing more has to
be done, then feel free to set the status to "resolved fixed" and close the issue

@mla: Thanks, but as it's not my bug I can't change status or close it!

fixed

closed