https://bugzilla.redhat.com/show_bug.cgi?id=1023727
Jan Zeleny <jzeleny(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |i18n-bugs(a)lists.fedoraproje
| |ct.org,
| |james.antill(a)redhat.com,
| |notting(a)redhat.com,
| |petersen(a)redhat.com,
| |pnemade(a)redhat.com
Component|yum |yum-langpacks
Assignee|packaging-team-maint@redhat |pnemade(a)redhat.com
|.com |
--- Comment #3 from Jan Zeleny <jzeleny(a)redhat.com> ---
Looks like another problem in yum-langpacks plugin, reassigning for further
evaluation.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=jOqoQ1wcIO&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1021907
Vratislav Podzimek <vpodzime(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|MODIFIED |POST
--- Comment #6 from Vratislav Podzimek <vpodzime(a)redhat.com> ---
The change has been reverted, but the scripts grabbing list of bugs to put into
an update didn't get that. Moving back to POST.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=mCPwuqnOrm&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1024188
Mike FABIAN <mfabian(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|mfabian(a)redhat.com |anaconda-maint-list@redhat.
| |com
--- Comment #1 from Mike FABIAN <mfabian(a)redhat.com> ---
In that first “welcome” screen, the only entry field is the field
below the language list where one can type a string to find
the desired language faster instead of just scrolling.
As soon as a language is selected and one proceeds to the next screen,
the default keyboard for the selected language/territory is
selected automatically according to what langtable returns.
For the "us" on the first “welcome” screen, langtable is not involved,
this is always just "us".
What else could it be?
Maybe somebody with a very different hardware keyboard like a French
AZERTY layout may have some problems to use the search field in that case.
But how could that be improved?
Showing a complicated dialog to select a keyboard layout only to make
searching the language in that rather simple list a bit easier
seems a bit overkill.
So I think it is OK as it is.
But certainly it has nothing to do with langtable, so I assign it back
to anaconda-maint-list(a)redhat.com to decide what to do.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=NTQYUT0fC6&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1024201
--- Comment #4 from Mike FABIAN <mfabian(a)redhat.com> ---
Although input method support during the installation might be an
interesting feature, its real usefulness is quite small, I think.
What else could it be useful for except for entering the real
user name in a script which requires an input method?
There is not much opportunity to enter text in one’s native language
during the installation, most stuff one enters there has to be ASCII
anyway like the login name or mount points.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ToLW9Ker6L&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1024201
--- Comment #3 from Mike FABIAN <mfabian(a)redhat.com> ---
Created attachment 817506
--> https://bugzilla.redhat.com/attachment.cgi?id=817506&action=edit
ubuntu-12.10-left-ubuntu-13.10-right.png
Ubuntu does not seem to support input methods during the installation either.
The left side of this screenshot is from the installation
of ubuntu-12.10-desktop-amd64.iso, the right side from
the installation of ubuntu-13.10-desktop-amd64.iso.
The screen during the installation where the real user name can be
entered is shown in both screen shots. That is the only place where I
can imagine an input method might have some use during the
installation. For example a Japanese user could write his name
correctly written in Japanes characters into the field for the "real
name" (not the login name).
One can see that in ubuntu 12.10, there were 2 keyboard icons on the
top, one of them is for ibus. Right clicking that one can show the
“about” message of ibus and also open the setup tool and add input
methods. Only 2 Chinese input methods are selectable, one of them is
“Pinyin”. But even after selecting that and clicking the right mouse
button on the name entry field and selecting
Input Methods -> IBus (Intelligent input Bus)
from the context menu, Chinese input still does not work.
Restarting ibus (from the context menu of the keyboard icon in the panel
at the top) does not help either.
In ubuntu 13.10, there is no keyboard icon at the top, ibus seems
not to be running at all. One can still open the context menu
of the name entry field, but selecting ibus there of course does not
achieve anything.
So this looks like Ubuntu does not support input methods during the
installation either at the moment.
I am not sure whether the running ibus in 12.10 was a failed attempt
to use input methods during the installation or an error.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=UkInlELESF&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=1021907
--- Comment #3 from Vratislav Podzimek <vpodzime(a)redhat.com> ---
(In reply to Adam Williamson from comment #2)
> Discussed at 2013-10-23 freeze exception review meeting:
> http://meetbot.fedoraproject.org/fedora-blocker-review/2013-10-23/f20-
> blocker-review.2013-10-23-16.00.log.txt . Rejected as a freeze exception
> issue: this is an entirely cosmetic and fairly trivial change to a vital and
> very fragile element of the installer, and that's a bad thing to take during
> a freeze period. This does not mean the change can't go into F20, but we'd
> prefer it be landed post-Beta, so we can catch any breakage early in Final
> testing without destabilizing Beta.
I'm sorry, but I've accidentally pushed the patch to the f20-branch as well as
to the master branch. Shall I revert it or could we give it a try and revert it
in case of some troubles? I've tested it and everything looks okay and working
as expected. Sorry for complicating things.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=j653SXcd8r&a=cc_unsubscribe