You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Justin Mclean <ju...@classsoftware.com> on 2013/05/29 02:52:39 UTC
Translations required for installer
Hi,
Can anyone translate "Select AIR and Flash Player versions." into Greek, Spanish, Dutch Portuguese , French or German?
It also also be useful to have the installer in a couple languages, eg Chinese where about 20% of our web site traffic comes from. Can anyone help out here?
Thanks,
Justin
Re: Translations required for installer
Posted by Lee Burrows <su...@leeburrows.com>.
I'm nit-picking.... but I've been given a slightly different Dutch translation:
Selecteer AIR en Flash Player versie
(singular "Version")
On 29/05/2013 08:20, Christophe Herreman wrote:
> Dutch: "Selecteer AIR en Flash Player versies"
>
>
> 2013/5/29 F M <a....@gmail.com>
>
>> German: "Bitte wählen Sie die AIR und Flash Player Versionen"
>> It is a more polite version "Please select AIR and Flash Player Version".
>> But i have also done the rest of the German translation it should fit that
>> style well.
>>
>>
>> 2013/5/29 Victor Hugo Garcia <vi...@gmail.com>
>>
>>> Spanish: "Seleccione las versiones de AIR y Flash Player"
>>> Portuguese: "Selecione as versões do AIR e Flash Player"
>>>
>>>
>>> 2013/5/28 Lee Burrows <su...@leeburrows.com>
>>>
>>>> Emailed my pal for a Dutch translation. Cant help with the rest.
>>>>
>>>>
>>>> On 29/05/2013 01:52, Justin Mclean wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Can anyone translate "Select AIR and Flash Player versions." into
>> Greek,
>>>>> Spanish, Dutch Portuguese , French or German?
>>>>>
>>>>> It also also be useful to have the installer in a couple languages, eg
>>>>> Chinese where about 20% of our web site traffic comes from. Can anyone
>>> help
>>>>> out here?
>>>>>
>>>>> Thanks,
>>>>> Justin
>>>>>
>>>>
>>>> --
>>>> Lee Burrows
>>>> ActionScripter
>>>>
>>>>
>
>
--
Lee Burrows
ActionScripter
Re: Translations required for installer
Posted by Christophe Herreman <ch...@gmail.com>.
Dutch: "Selecteer AIR en Flash Player versies"
2013/5/29 F M <a....@gmail.com>
> German: "Bitte wählen Sie die AIR und Flash Player Versionen"
> It is a more polite version "Please select AIR and Flash Player Version".
> But i have also done the rest of the German translation it should fit that
> style well.
>
>
> 2013/5/29 Victor Hugo Garcia <vi...@gmail.com>
>
> > Spanish: "Seleccione las versiones de AIR y Flash Player"
> > Portuguese: "Selecione as versões do AIR e Flash Player"
> >
> >
> > 2013/5/28 Lee Burrows <su...@leeburrows.com>
> >
> > > Emailed my pal for a Dutch translation. Cant help with the rest.
> > >
> > >
> > > On 29/05/2013 01:52, Justin Mclean wrote:
> > >
> > >> Hi,
> > >>
> > >> Can anyone translate "Select AIR and Flash Player versions." into
> Greek,
> > >> Spanish, Dutch Portuguese , French or German?
> > >>
> > >> It also also be useful to have the installer in a couple languages, eg
> > >> Chinese where about 20% of our web site traffic comes from. Can anyone
> > help
> > >> out here?
> > >>
> > >> Thanks,
> > >> Justin
> > >>
> > >
> > >
> > > --
> > > Lee Burrows
> > > ActionScripter
> > >
> > >
> >
>
--
Christophe Herreman
http://www.herrodius.com
http://www.springactionscript.org
http://www.as3commons.org
Re: Translations required for installer
Posted by F M <a....@gmail.com>.
German: "Bitte wählen Sie die AIR und Flash Player Versionen"
It is a more polite version "Please select AIR and Flash Player Version".
But i have also done the rest of the German translation it should fit that
style well.
2013/5/29 Victor Hugo Garcia <vi...@gmail.com>
> Spanish: "Seleccione las versiones de AIR y Flash Player"
> Portuguese: "Selecione as versões do AIR e Flash Player"
>
>
> 2013/5/28 Lee Burrows <su...@leeburrows.com>
>
> > Emailed my pal for a Dutch translation. Cant help with the rest.
> >
> >
> > On 29/05/2013 01:52, Justin Mclean wrote:
> >
> >> Hi,
> >>
> >> Can anyone translate "Select AIR and Flash Player versions." into Greek,
> >> Spanish, Dutch Portuguese , French or German?
> >>
> >> It also also be useful to have the installer in a couple languages, eg
> >> Chinese where about 20% of our web site traffic comes from. Can anyone
> help
> >> out here?
> >>
> >> Thanks,
> >> Justin
> >>
> >
> >
> > --
> > Lee Burrows
> > ActionScripter
> >
> >
>
Re: Translations required for installer
Posted by Victor Hugo Garcia <vi...@gmail.com>.
Spanish: "Seleccione las versiones de AIR y Flash Player"
Portuguese: "Selecione as versões do AIR e Flash Player"
2013/5/28 Lee Burrows <su...@leeburrows.com>
> Emailed my pal for a Dutch translation. Cant help with the rest.
>
>
> On 29/05/2013 01:52, Justin Mclean wrote:
>
>> Hi,
>>
>> Can anyone translate "Select AIR and Flash Player versions." into Greek,
>> Spanish, Dutch Portuguese , French or German?
>>
>> It also also be useful to have the installer in a couple languages, eg
>> Chinese where about 20% of our web site traffic comes from. Can anyone help
>> out here?
>>
>> Thanks,
>> Justin
>>
>
>
> --
> Lee Burrows
> ActionScripter
>
>
Re: Translations required for installer
Posted by Lee Burrows <su...@leeburrows.com>.
Emailed my pal for a Dutch translation. Cant help with the rest.
On 29/05/2013 01:52, Justin Mclean wrote:
> Hi,
>
> Can anyone translate "Select AIR and Flash Player versions." into Greek, Spanish, Dutch Portuguese , French or German?
>
> It also also be useful to have the installer in a couple languages, eg Chinese where about 20% of our web site traffic comes from. Can anyone help out here?
>
> Thanks,
> Justin
--
Lee Burrows
ActionScripter
Re: Releasing a new SDK/installer
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> When you are branching off a conversation into a new thread, please keep
> the old email history in the new thread.
I replied and changed the subject which should do that depending on your email client. I think gmail has issues with this.
Justin
Re: Releasing a new SDK/installer
Posted by OmPrakash Muppirala <bi...@gmail.com>.
<meta>
When you are branching off a conversation into a new thread, please keep
the old email history in the new thread. This way we will have the
relevant conversations in one thread. Our future selves will thank us for
this.
Thanks,
Om
On Wed, May 29, 2013 at 9:25 PM, Justin Mclean <ju...@classsoftware.com>wrote:
> Hi,
>
> > OK, what happens for 4.11 if we don't need to change the installer? How
> > do we test the RC then while others are downloading 4.10?
>
> The SDK RC I assume you mean? We don't have to use the installer to test
> the Flex SDK release candidate.
>
> But if you do want to test the installer you can either:
> a) Use a modified installer by setting configOveride variable inside it to
> point to a new config file.
> b) Use the released installer and pass the config file via the command
> line to the installer.
>
> Once the SDK is released it a simple matter of changing the public config
> file and testing that it works. If in the unlikely case it doesn't work we
> can just revert back to the old config file while we fix the issue. We can
> do this before we announce the new release.
>
> Thanks,
> Justin
Releasing a new SDK/installer
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> OK, what happens for 4.11 if we don't need to change the installer? How
> do we test the RC then while others are downloading 4.10?
The SDK RC I assume you mean? We don't have to use the installer to test the Flex SDK release candidate.
But if you do want to test the installer you can either:
a) Use a modified installer by setting configOveride variable inside it to point to a new config file.
b) Use the released installer and pass the config file via the command line to the installer.
Once the SDK is released it a simple matter of changing the public config file and testing that it works. If in the unlikely case it doesn't work we can just revert back to the old config file while we fix the issue. We can do this before we announce the new release.
Thanks,
Justin
Re: Translations required for installer
Posted by Alex Harui <ah...@adobe.com>.
On 5/29/13 4:00 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>
>> But I thought there was an issue about not wanting to update the config
>> file until the RC is approved so the general public doesn't start
>> installing the RC, but we (the voters) want to test that the installer
>> will work against that RC.
>>
>
>Luckily, we are introducing a new version of the installer config xml this
>time. The config version is baked into the Installer source code. So,
>there is no way that existing Installers can access the new config xml.
> The Installer RC will be able to test the sdk RC and the sdk release
>versions fine.
OK, what happens for 4.11 if we don't need to change the installer? How
do we test the RC then while others are downloading 4.10?
Thanks,
-Alex
Re: Translations required for installer
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Wed, May 29, 2013 at 3:54 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
> >>
> >The installer config xml is the only file we need to change a new flex-sdk
> >release. The installer itself does not need to change.
> Except in this case where we are making improvements to the installer as
> well?
>
That's correct.
>
> But I thought there was an issue about not wanting to update the config
> file until the RC is approved so the general public doesn't start
> installing the RC, but we (the voters) want to test that the installer
> will work against that RC.
>
Luckily, we are introducing a new version of the installer config xml this
time. The config version is baked into the Installer source code. So,
there is no way that existing Installers can access the new config xml.
The Installer RC will be able to test the sdk RC and the sdk release
versions fine.
Om
Re: Translations required for installer
Posted by Alex Harui <ah...@adobe.com>.
>>
>The installer config xml is the only file we need to change a new flex-sdk
>release. The installer itself does not need to change.
Except in this case where we are making improvements to the installer as
well?
But I thought there was an issue about not wanting to update the config
file until the RC is approved so the general public doesn't start
installing the RC, but we (the voters) want to test that the installer
will work against that RC.
-Alex
Re: Translations required for installer
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Wed, May 29, 2013 at 3:45 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
> On 5/29/13 3:40 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
> >> >Also, the last time we released the Installer, there was general
> >>confusion
> >> >with people thinking that we are releasing a new version of the SDK.
> >>We
> >> >should try to release new versions of the sdk and the installer as
> >>much as
> >> >possible.
> >> IIRC, there is some reason we can't release them together. Isn't it
> >>that
> >> the Installer can't be certified to install the latest SDK until we put
> >> the SDK in its final URL? I think in the past we release the SDK then
> >> start futzing with the Installer and several days/weeks go by. What
> >>would
> >> it take for us to feel good about releasing the Installer the same day
> >>or
> >> next day after an SDK release?
> >>
> >>
> >Depends on when we announce the release. Here is what I would prefer:
> >
> >1. Get flex-sdk and flex-installer both release ready
> >2. Generate the flex-sdk release artifacts
> >3. Call for a vote for flex-sdk release
> >4. Upload flex-sdk artifacts to dist.
> >5.a Wait for 24 hours for mirrors to propagate
> >5.b Generate flex-installer artifacts
> >6. Call for a vote for flex-installer release
> >7. Upload flex-installer artifacts to dist.
> >8. Wait for 24 hours for mirrors to propagate.
> >9. Announce flex-sdk 4.10 and flex-installer 2.6 release
> >
> >Thoughts?
> Seems reasonable. But isn't there some code we need to add in step 1 in
> order to get the installer release ready? Like getting it to somehow look
> at the RC's location to install from?
>
> -Alex
>
>
The installer config xml is the only file we need to change a new flex-sdk
release. The installer itself does not need to change.
Om
Re: Translations required for installer
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Wed, May 29, 2013 at 3:49 PM, Justin Mclean <ju...@classsoftware.com>wrote:
> Hi,
>
> Isn't now just this?
>
> 1. Get fles-sdk ready
> 2. Vote on flex-sdk
> 3. update installer config file
> 4. Update to dist
> 5. Wait 24 hours
> 6. Announce
>
> ie there's no need to release a new installer each time we release a Flex
> SDK as it pick up the new version from the config file.
>
>
That is correct.
Om
Re: Translations required for installer
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Isn't now just this?
1. Get fles-sdk ready
2. Vote on flex-sdk
3. update installer config file
4. Update to dist
5. Wait 24 hours
6. Announce
ie there's no need to release a new installer each time we release a Flex SDK as it pick up the new version from the config file.
Thanks,
Justin
Re: Translations required for installer
Posted by Alex Harui <ah...@adobe.com>.
On 5/29/13 3:40 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>> >Also, the last time we released the Installer, there was general
>>confusion
>> >with people thinking that we are releasing a new version of the SDK.
>>We
>> >should try to release new versions of the sdk and the installer as
>>much as
>> >possible.
>> IIRC, there is some reason we can't release them together. Isn't it
>>that
>> the Installer can't be certified to install the latest SDK until we put
>> the SDK in its final URL? I think in the past we release the SDK then
>> start futzing with the Installer and several days/weeks go by. What
>>would
>> it take for us to feel good about releasing the Installer the same day
>>or
>> next day after an SDK release?
>>
>>
>Depends on when we announce the release. Here is what I would prefer:
>
>1. Get flex-sdk and flex-installer both release ready
>2. Generate the flex-sdk release artifacts
>3. Call for a vote for flex-sdk release
>4. Upload flex-sdk artifacts to dist.
>5.a Wait for 24 hours for mirrors to propagate
>5.b Generate flex-installer artifacts
>6. Call for a vote for flex-installer release
>7. Upload flex-installer artifacts to dist.
>8. Wait for 24 hours for mirrors to propagate.
>9. Announce flex-sdk 4.10 and flex-installer 2.6 release
>
>Thoughts?
Seems reasonable. But isn't there some code we need to add in step 1 in
order to get the installer release ready? Like getting it to somehow look
at the RC's location to install from?
-Alex
Re: Translations required for installer
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Wed, May 29, 2013 at 3:29 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
> On 5/29/13 3:20 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
> >On Wed, May 29, 2013 at 3:14 PM, Justin Mclean
> ><ju...@classsoftware.com>wrote:
> >
> >> Hi,
> >>
> >> > We should release it along with the next SDK release, IMO.
> >>
> >> There noting dependant on the new SDK and selecting the Air/FP version
> >>is
> >> useful to people now. There needs to be a separate release/vote cycle
> >>for
> >> it so it may be hard to release them both at exactly the same time.
> >>
> >> Thanks,
> >> Justin
> >
> >
> >The flex-sdk release generates a lot of buzz. The Installer can benefit
> >from that kind of buzz. It does not make sense to repeat the marketing
> >efforts if we are going to release 4.10 in short order.
> >
> >Also, the last time we released the Installer, there was general confusion
> >with people thinking that we are releasing a new version of the SDK. We
> >should try to release new versions of the sdk and the installer as much as
> >possible.
> IIRC, there is some reason we can't release them together. Isn't it that
> the Installer can't be certified to install the latest SDK until we put
> the SDK in its final URL? I think in the past we release the SDK then
> start futzing with the Installer and several days/weeks go by. What would
> it take for us to feel good about releasing the Installer the same day or
> next day after an SDK release?
>
>
Depends on when we announce the release. Here is what I would prefer:
1. Get flex-sdk and flex-installer both release ready
2. Generate the flex-sdk release artifacts
3. Call for a vote for flex-sdk release
4. Upload flex-sdk artifacts to dist.
5.a Wait for 24 hours for mirrors to propagate
5.b Generate flex-installer artifacts
6. Call for a vote for flex-installer release
7. Upload flex-installer artifacts to dist.
8. Wait for 24 hours for mirrors to propagate.
9. Announce flex-sdk 4.10 and flex-installer 2.6 release
Thoughts?
> >
> >Thanks,
> >Om
>
>
Re: Translations required for installer
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> The flex-sdk release generates a lot of buzz. The Installer can benefit
> from that kind of buzz. It does not make sense to repeat the marketing
> efforts if we are going to release 4.10 in short order.
How close are we to releasing 4.10? Closer than a few weeks ago but still quite a bit to do.
https://issues.apache.org/jira/browse/FLEX-33546
> Also, the last time we released the Installer, there was general confusion
> with people thinking that we are releasing a new version of the SDK.
There is that.
Justin
Re: Translations required for installer
Posted by OmPrakash Muppirala <bi...@gmail.com>.
>
> It would be great to just have a 24-hour gap by making the installer
> capable of installing an RC.
>
>
This capability exists today. A relative path to the flex-sdk (i.e.
without a http at the beginning) will cause the Installer to resolve a
mirror based url.
An absolute path (with a 'http' at the beginning) will use the files
directly from the source. We can point this to the Release Candidate for
testing the Installer (and the sdk release itself)
But again, I wont be very comfortable releasing the installer without
personally watching it download the flex-sdk release binary from a mirror
url on my machine. Thats just me...
Om
Re: Translations required for installer
Posted by Alex Harui <ah...@adobe.com>.
On 5/29/13 3:43 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>Hi,
>
>> IIRC, there is some reason we can't release them together.
>They require separate release candidate and votes. Vote on both at once
>may stretch out the process is my concern.
Well, to get Om's 24 hour goal, we'd have to have both votes open at the
same time and close out the SDK vote first. I'm not sure how bad that
will be. Then we can use the installer as another way of testing the
SDK's binary kit.
>
>> Isn't it that the Installer can't be certified to install the latest
>>SDK until we put
>> the SDK in its final URL?
>When we release a new SDK all we have to do it update the config file for
>the installer to pick it up so it should be easier this time.
My concern here is that historically, I think we don't get serious about
testing the installer until the vote thread starts and then there is a
minimum 72 hours and then we get feedback about issues from folks and
create more RC's and vote threads and time just seems to slip by.
It would be great to just have a 24-hour gap by making the installer
capable of installing an RC.
-Alex
Re: Translations required for installer
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> IIRC, there is some reason we can't release them together.
They require separate release candidate and votes. Vote on both at once may stretch out the process is my concern.
> Isn't it that the Installer can't be certified to install the latest SDK until we put
> the SDK in its final URL?
When we release a new SDK all we have to do it update the config file for the installer to pick it up so it should be easier this time.
Thanks,
Justin
Re: Translations required for installer
Posted by Alex Harui <ah...@adobe.com>.
On 5/29/13 3:20 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>On Wed, May 29, 2013 at 3:14 PM, Justin Mclean
><ju...@classsoftware.com>wrote:
>
>> Hi,
>>
>> > We should release it along with the next SDK release, IMO.
>>
>> There noting dependant on the new SDK and selecting the Air/FP version
>>is
>> useful to people now. There needs to be a separate release/vote cycle
>>for
>> it so it may be hard to release them both at exactly the same time.
>>
>> Thanks,
>> Justin
>
>
>The flex-sdk release generates a lot of buzz. The Installer can benefit
>from that kind of buzz. It does not make sense to repeat the marketing
>efforts if we are going to release 4.10 in short order.
>
>Also, the last time we released the Installer, there was general confusion
>with people thinking that we are releasing a new version of the SDK. We
>should try to release new versions of the sdk and the installer as much as
>possible.
IIRC, there is some reason we can't release them together. Isn't it that
the Installer can't be certified to install the latest SDK until we put
the SDK in its final URL? I think in the past we release the SDK then
start futzing with the Installer and several days/weeks go by. What would
it take for us to feel good about releasing the Installer the same day or
next day after an SDK release?
>
>Thanks,
>Om
Re: Translations required for installer
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Wed, May 29, 2013 at 3:14 PM, Justin Mclean <ju...@classsoftware.com>wrote:
> Hi,
>
> > We should release it along with the next SDK release, IMO.
>
> There noting dependant on the new SDK and selecting the Air/FP version is
> useful to people now. There needs to be a separate release/vote cycle for
> it so it may be hard to release them both at exactly the same time.
>
> Thanks,
> Justin
The flex-sdk release generates a lot of buzz. The Installer can benefit
from that kind of buzz. It does not make sense to repeat the marketing
efforts if we are going to release 4.10 in short order.
Also, the last time we released the Installer, there was general confusion
with people thinking that we are releasing a new version of the SDK. We
should try to release new versions of the sdk and the installer as much as
possible.
Thanks,
Om
Re: Translations required for installer
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> We should release it along with the next SDK release, IMO.
There noting dependant on the new SDK and selecting the Air/FP version is useful to people now. There needs to be a separate release/vote cycle for it so it may be hard to release them both at exactly the same time.
Thanks,
Justin
Re: Translations required for installer
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On May 29, 2013 2:32 AM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
> Hi,
>
> Thanks everyone for helping that's been checked into develop branch of
the installer.
>
> IMO it's probably good enough for a 2.6 release candidate and vote.
>
We should release it along with the next SDK release, IMO.
Thanks,
Om
> Thanks,
> Justin
Re: Translations required for installer
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Thanks everyone for helping that's been checked into develop branch of the installer.
IMO it's probably good enough for a 2.6 release candidate and vote.
Thanks,
Justin
Re: Translations required for installer
Posted by Frédéric THOMAS <we...@hotmail.com>.
French: Sélectionnez les versions de AIR et du Player Flash
Not sure about the translation, as written it implies there are more than
one version of AIR and Flash Player to select, if there is one to choose for
each of them, the translation is:
Sélectionnez la version de AIR et du Player Flash
-----Message d'origine-----
From: Justin Mclean
Sent: Wednesday, May 29, 2013 2:52 AM
To: dev@flex.apache.org
Subject: Translations required for installer
Hi,
Can anyone translate "Select AIR and Flash Player versions." into Greek,
Spanish, Dutch Portuguese , French or German?
It also also be useful to have the installer in a couple languages, eg
Chinese where about 20% of our web site traffic comes from. Can anyone help
out here?
Thanks,
Justin