Hi all,
as promised I thought about a new structure and have created the
following websites to ease the download of RC builds:
http://download.openoffice.org/next/other_rc.html
http://download.openoffice.org/next/langpack_rc.html
Please have a look if the names of the languages are correct.
2009/11/2 Marcus Lange marcus.la...@sun.com:
Hi all,
Hello,
as promised I thought about a new structure and have created the following
websites to ease the download of RC builds:
http://download.openoffice.org/next/other_rc.html
The first sentence on this page mentions langpacks, although
Hi Marcus,
thanks for your work! :) I have a few notes though. Or basically, maybe
it's just one note.
How visible will those builds be? I think we've agreed that they should
be visible, and I'm not so sure hiding them behind Download - Get More
Platforms and Languages - Developer Snapshots -
Martin Srebotnjak wrote:
Hi Martin,
as promised I thought about a new structure and have created the following
websites to ease the download of RC builds:
http://download.openoffice.org/next/other_rc.html
The first sentence on this page mentions langpacks, although the page
actually lists
Rimas Kudelis wrote:
Hi Rimas,
thanks for your work! :) I have a few notes though. Or basically, maybe
it's just one note.
How visible will those builds be? I think we've agreed that they should
I haven't seen the agreement. In which mail was it?
be visible, and I'm not so sure hiding
Hi Marcus, *,
not sure why this slipped my radar, but still:
On Fri, Oct 16, 2009 at 5:11 PM, Marcus Lange marcus.la...@sun.com wrote:
Christian Lohmaier wrote:
On Thu, Oct 15, 2009 at 3:32 PM, Marcus Lange marcus.la...@sun.com
wrote:
if there wouldn't be a QA for langpacks, then they
Marcus Lange wrote:
I would propose to merge the two pages you created with main
http://download.openoffice.org/other.html and
http://download.openoffice.org/langpack.html respectively.
I've tried this but don't liked it because IMHO this is too much content
for a single page.
Untested
Hello,
maybe the verified builds would get a green check mark icon, and the others
a red question mark icon? There should also be a legend stating that builds
with the green check mark are supported and verified, whereas the others
might not work as expected. That being said, they can all be put
Hi Marcus,
Thanks for the update.
Could you please remove Gujarati (gu-IN)? because there is only one Gujarati
language.
Thanks!
Ankit
--- On Mon, 2/11/09, Marcus Lange marcus.la...@sun.com wrote:
From: Marcus Lange marcus.la...@sun.com
Subject: [l10n-dev] Re: Re: New home for downloading
2009.11.02 15:52, Marcus Lange rašė:
Marcus Lange wrote:
I would propose to merge the two pages you created with main
http://download.openoffice.org/other.html and
http://download.openoffice.org/langpack.html respectively.
I've tried this but don't liked it because IMHO this is too much
Ankit Patel wrote:
Thanks for the update.
Could you please remove Gujarati (gu-IN)? because there is only one Gujarati
language.
sure, so we should also cancel the gu-IN build at all? It would be build
again for 3.2.0.
Best regards
Marcus
--- On Mon, 2/11/09, Marcus Lange
Hi again,
thanks for your work! :) I have a few notes though. Or basically, maybe
it's just one note.
How visible will those builds be? I think we've agreed that they should
I haven't seen the agreement. In which mail was it?
I think this whole thread (or at least the sub-thread) is about
Rimas Kudelis wrote:
Hi Rimas,
OK, with the hint of Untested it could work. I've to play with this
setup.
I tried to start with this but I still think we should not mix stable
and unstable builds together:
- even so all builds for Mac OS PPC (which are done by Maho) have to be
integrsted,
Martin Srebotnjak wrote:
Hi Martin,
maybe the verified builds would get a green check mark icon, and the others
a red question mark icon? There should also be a legend stating that builds
with the green check mark are supported and verified, whereas the others
might not work as expected. That
Hi,
IMHO nobody has said this. ;-) We are doing full install sets when the
L10N has reached 75 or 80 %. Langpacks are always done.
Sun Hamburg team is doing full builds if
at least 80% UI has been translated and at least 80% help content has
been translated
Sun Hamburg team is building
Interesting, I have several years UI translation between 99-100% and
Help over 90 and always stated it when submitting translations. Though
I havent seen full builds exept pre-last release when I asked Ivo to
make a build for win32.
ain
On Mon, Nov 2, 2009 at 18:11, Joost Andrae
Hi all,
as an alternative I've created a langpack website with all files listed
in 2 tables:
http://download.openoffice.org/next/langpack_all.html
Maybe we can agree on this as commpromise?
Best regards
Marcus
Marcus Lange wrote:
Hi all,
as promised I thought about a new structure and
Hi, I think this is better.
Why are the untested builds marked as RC2? I mean, you already divided the
tested/approved and untested builds into two tables, why make users wonder
if this RC2 might mean this is not really 3.1.1 (or whatever the latest
version is)?
Yes, they are not released so
Hi Ankit,
in the draft websites I've deleted the gu-IN entry.
In order to cancel any new build and to document this work please file
an issue and assign it to Ivo Hinkelmann (ihi). Tell him to make sure
that no translation will be lost and to compare the gu and gu-IN files:
Wouldn't this table look much better, if it was only one?
And if the tested/release versions cells would have a green background
indicating these are the ones that are green-state in QA?
It confuses user if she finds her language in the first table but not the OS
she looked for (yeah, it is
Martin Srebotnjak wrote:
Hi Martin,
Hi, I think this is better.
Why are the untested builds marked as RC2? I mean, you already divided the
tested/approved and untested builds into two tables, why make users wonder
if this RC2 might mean this is not really 3.1.1 (or whatever the latest
version
2009/11/2 Marcus Lange marcus.la...@sun.com
because it is the official suffix before it get tested and released. It's
the same with a beta release.
Yes, they are not released so they remain release candidates, but actually
the actual code is same as released version. I think this degrades
Martin Srebotnjak wrote:
2009/11/2 Marcus Lange marcus.la...@sun.com
because it is the official suffix before it get tested and released. It's
the same with a beta release.
Yes, they are not released so they remain release candidates, but actually
the actual code is same as released
Martin Srebotnjak wrote:
Hi Martin,
Wouldn't this table look much better, if it was only one?
And if the tested/release versions cells would have a green background
indicating these are the ones that are green-state in QA?
the question is not if it looks better but if it would be an
2009/11/2 Marcus Lange marcus.la...@sun.com
BTW:
Please don't hit me when I use Firefox as example ;-) but Mozilla has also
split it up (fully localized and beta):
http://www.mozilla.com/en-US/firefox/all.html
I am localizing many OS software packages, but not even one requires QA for
every
Hi,
I'm forwarding a question brought to me:
Why aren't the Icelandic translations available on the CVS
server? I have always been fetching the latest
localizations from
anoncvs.services.openoffice.org/cvs/l10n/l10n/source.
Is it obsolete?
Is there any other place we could parse the .po files
26 matches
Mail list logo
