[Cooker] Why there is no Chinese One?

[Funda Wang]

Hello,

Are there any reasons that we do not promote that asia version of
Mandriva One acturally support Chinese?

Regards.

[Frederic Crozat]

Le jeudi 05 novembre 2009 à 16:54 +0800, Funda Wang a écrit :
> Hello,
>
> Are there any reasons that we do not promote that asia version of
> Mandriva One acturally support Chinese?

Well, last time I checked, China was part of Asia and One releases are
available in an Asia version for both GNOME and KDE.

I don't see a problme here.


--
Frederic Crozat <fcrozat@...>
Mandriva

[Funda Wang]

2009/11/5 Frederic Crozat <fcrozat@...>:

> Le jeudi 05 novembre 2009 à 16:54 +0800, Funda Wang a écrit :
>> Hello,
>>
>> Are there any reasons that we do not promote that asia version of
>> Mandriva One acturally support Chinese?
>
> Well, last time I checked, China was part of Asia and One releases are
> available in an Asia version for both GNOME and KDE.
>
> I don't see a problme here.

1. They are not listed in *.iso.langs
2. They are not listed in Mandriva wiki (I've corrected it already)
3. They are not available in mandriva.com's download page.
>
>
> --
> Frederic Crozat <fcrozat@...>
> Mandriva
>
>

[Christophe Fergeau-3]

Hi Funda,

Funda Wang a écrit :
> 1. They are not listed in *.iso.langs
> 2. They are not listed in Mandriva wiki (I've corrected it already)
> 3. They are not available in mandriva.com's download page.
>  

It seems something went wrong in the generation of the .langs files
which were then used to fill the wiki and the download pages. I just
checked the KDE and GNOME asia Ones can be set to Chinese. I'm looking
at why some languages are missing from the .langs files.

Sorry for the inconvenience and thanks for noticing it!

Christophe

[Thomas Lottmann]

Hello!

I am under 2010 now with the new design (went from Cooker to 2010.0), I
even reinstalled the new powerpack theme package, but it won't change
anything, all the KDE splashes still end up on a weird black/white/bluey
screen when it shoudl be displaying "Loading desktop" or whatever is the
last text status.

So what was supposed to solve the issue did not solve it.

[Dimitrios]

I have always the big white square on the middle left of the screen during the login in plasma

2009/11/5 Thomas Lottmann <skipercooker@...>

Hello!

I am under 2010 now with the new design (went from Cooker to 2010.0), I even reinstalled the new powerpack theme package, but it won't change anything, all the KDE splashes still end up on a weird black/white/bluey screen when it shoudl be displaying "Loading desktop" or whatever is the last text status.

So what was supposed to solve the issue did not solve it.

[Thomas Lottmann]

Dimitrios Glentadakis a écrit :

> I have always the big white square on the middle left of the screen
> during the login in plasma
>
> 2009/11/5 Thomas Lottmann <skipercooker@...
> <mailto:skipercooker@...>>
>
>     Hello!
>
>     I am under 2010 now with the new design (went from Cooker to
>     2010.0), I even reinstalled the new powerpack theme package, but it
>     won't change anything, all the KDE splashes still end up on a weird
>     black/white/bluey screen when it shoudl be displaying "Loading
>     desktop" or whatever is the last text status.
>
>     So what was supposed to solve the issue did not solve it.
>
>

That's what I am trying to describe. :)

On Thu, Nov 5, 2009 at 5:02 PM, Thomas Lottmann <skipercooker@...> wrote:

> Dimitrios Glentadakis a écrit :
>>
>> I have always the big white square on the middle left of the screen during
>> the login in plasma
>>
>> 2009/11/5 Thomas Lottmann <skipercooker@...
>> <mailto:skipercooker@...>>
>>
>>    Hello!
>>
>>    I am under 2010 now with the new design (went from Cooker to
>>    2010.0), I even reinstalled the new powerpack theme package, but it
>>    won't change anything, all the KDE splashes still end up on a weird
>>    black/white/bluey screen when it shoudl be displaying "Loading
>>    desktop" or whatever is the last text status.
>>
>>    So what was supposed to solve the issue did not solve it.
>>
>>
>
> That's what I am trying to describe. :)
>

I just want to say that the qt bug I thought caused the problem did
not cause the problem after all as neoclust built a patched version
for me which did solve all my other problems but not this one (it
could still be a qt problem though but another one)