On Wed, May 21, 2014 at 02:48:44PM -0000, Stéphane Graber wrote:
> On Wed, May 21, 2014 at 09:34:08AM -0400, Barry Warsaw wrote:
> > On May 21, 2014, at 09:22 AM, Iain Lane wrote:
> >
> > >what are we supposed to do with those descriptions? Perhaps this means that
> > >the server isn't providing what we want yet?
> >
> > At one time, the server was going to give i18n'd human readable descriptions.
> > I don't know whether the current behavior is because the ui couldn't do
> > anything with them, or whether the information is not available when the
> > server crafts the index.json files. If the i18n descriptions won't be
> > available on the server, then it seems pointless to want to expose i18n
> > descriptions in the API and ui. If that's the case, let's close this bug as
> > won't fix. Stephane?
>
> So far we've never bothered write those descriptions (I just put the
> channel info in the description at the moment) or get any of that
> translated, but I'd expect that when we hit RTM we'll be asked to do it.
>
>
> Pushing updates to end users without a localized description is IMO
> unacceptable, so this feature is still going to be required down the
> line.
So that we can implement this, could you put some dummy information in
there? It can be just lorem ipsum in a few languages (not actually
translated), but it'll be enough to write the user interface and then we
can actually display it when it is provided properly.
On Wed, May 21, 2014 at 02:48:44PM -0000, Stéphane Graber wrote:
> On Wed, May 21, 2014 at 09:34:08AM -0400, Barry Warsaw wrote:
> > On May 21, 2014, at 09:22 AM, Iain Lane wrote:
> >
> > >what are we supposed to do with those descriptions? Perhaps this means that
> > >the server isn't providing what we want yet?
> >
> > At one time, the server was going to give i18n'd human readable descriptions.
> > I don't know whether the current behavior is because the ui couldn't do
> > anything with them, or whether the information is not available when the
> > server crafts the index.json files. If the i18n descriptions won't be
> > available on the server, then it seems pointless to want to expose i18n
> > descriptions in the API and ui. If that's the case, let's close this bug as
> > won't fix. Stephane?
>
> So far we've never bothered write those descriptions (I just put the
> channel info in the description at the moment) or get any of that
> translated, but I'd expect that when we hit RTM we'll be asked to do it.
>
>
> Pushing updates to end users without a localized description is IMO
> unacceptable, so this feature is still going to be required down the
> line.
So that we can implement this, could you put some dummy information in
there? It can be just lorem ipsum in a few languages (not actually
translated), but it'll be enough to write the user interface and then we
can actually display it when it is provided properly.
--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]