[PATCH 2/2] Add language support spoke

Chris Lumens clumens at redhat.com
Tue Apr 16 16:56:54 UTC 2013


> Yes, I noticed the command and thought about it.One difference
> here is that with current approach you can't add additional support
> without specifying lang (system language). Is it worse or better?
> To me it seems less comfortable (no option to just go with default
> lang and add additional one with langsupport command), but I think
> it is also more clear in a way (e.g. is it clear that when using
> onlylangsupport command, default system lang will be used?).

Okay, I think having what you've originally come up with is for the
best, then.  If the behavior is different from the previous langsupport
command, then it's going to be more confusing.  Also, I don't believe
we've removed a command and then brought it back later.  Doing so would
create this weird time where it wasn't supported, followed by different
support.

It's even confusing to talk about.

> >What happens if I select a lot of languages to add?
> 
> They are ellipsized in the status. Do you think we should display only
> system lang (data.lang.lang) - similar as withdefault keyboard and
> keyboard spoke? Maybebut one thing is that it can't be changed in
> the spoke sothe status wouldn't reflect any changes in the spoke
> actually. Perhapswe can make the system lang (which comes first)
> more prominent?

Ah, I'd forgotten that the ellipses thing was global.  That might read
kind of funny, though.  If you do want to make the system language show
first, you could make the string something like:  "%s and others", where
%s is the system language.  There might be better ways of wording that.
it was just the first thing that came to mind.

- Chris


More information about the anaconda-patches mailing list