touch-packages team mailing list archive

[Raphael das Neves Calvo <raphael.calvo@xxxxxxxxx>]

We can find some "evidence" of what I am saying here about the Latin Code
page for MS-DOS.

http://www.dosbox.com/wiki/KEYB

Here follows a screenshot of the MS-DOS  character set setup a.k.a.
codepage).


Note that in the keyboard code in Brazil is Empty... That is because on
that time in history we did not have a keyboard. Only in the 90's that we
standardized a Brazilian keyboard (ABNT2).

You can also note that for EVERY Latin country the carachter set was code
page 437 which in "modern" versions of MS-DOS (I believe since MS-DOS 5.0)
was superseded by code page 850.

The only thing that changes is the keyboard layout (for countries that had
their own layouts) but the combination of symbols and letters to represent
a new one such as ç was the same independent of the keyboard chosen.

Since in Brazil we did not have a specific keyboard we used the US
International (code 103) with the code page set to 850.

Portugal had their own keyboard layout but if they were using the US
international keyboard layout the behavior was the same as here in Brazil.

... Maybe this help...

Regards

Calvo

On Fri, Apr 3, 2015, 09:44 Raphael Calvo <raphael.calvo@xxxxxxxxx>
wrote:

> One more thing...
>
> In the glory days of DR-DOS/MS-DOS, if I am not mistaken,  there was no
> keyboard setup specially made for Brazil regarding US International
> keyboard. It was a setup for Latin languages, I.e., every country that has
> a latin language was affected (French, portuguese, Italian...)
>
> Regards
>
> Calvo
>
> On Fri, Apr 3, 2015, 09:39 Raphael Calvo <raphael.calvo@xxxxxxxxx> wrote:
>
>> Gunnar,
>>
>> My guess here is based on history but maybe I am wrong....
>> The reason we Brazilians use the US international keyboard so much is
>> because in the '70s and '80s we didn't have a national industry to cope
>> with our internal demands for products related to computers. Almost every
>> single computer we had was imported (leggaly or illegally) from USA or it
>> was a clone made by our industry based on an US computer model.
>>
>> Portugal may have had a similar issue (I am especulating here) because
>> they were also under a dictatorship for some time, but in their case if a
>> similar situation occurred than they would probably had access to some
>> design made in Europe instead of something from US. Again, I am
>> especulating... It is just a theory but Leandro pointed out that he made a
>> brief research about this issue being relevant to Portuguese people and he
>> found some links to substantiate the claim that Portugueses would be
>> benefited from this fix.
>>
>> Kind Regards
>>
>> Calvo
>>
>> On Thu, Apr 2, 2015, 19:50 Gunnar Hjalmarsson <518056@xxxxxxxxxxxxxxxxxx>
>> wrote:
>>
>>> Thanks for your comments re pt_PT, Leandro.
>>>
>>> As long as we consider setting LC_CTYPE, in any of the ways mentioned in
>>> comment #96, a fix, it should be noted that '+c results in ç
>>> irrespective of which keyboard layout you use. In other words, the
>>> changed behavior is not conditioned by the use of an English US
>>> international keyboard layout, as Raphael suggested in comment #98. I
>>> assume that this was considered a reasonable behavior for Brazilian
>>> users, considering which physical keyboards are typically used in
>>> Brazil.
>>>
>>> We could propose a change to the libx11 package which adds a
>>> /usr/share/X11/locale/pt_PT.UTF-8/Compose file. But before proposing
>>> such a change I would like to ask if it would make as much sense for
>>> users living in Portugal as the corresponding Brazilian file makes for
>>> users living in Brazil.
>>>
>>> * Do users who live in Portugal use an English US international
>>>   keyboard layout as often as Brazilian users do, or do they typically
>>>   use some Portuguese keyboard layout?
>>>
>>> * Since the behavior may make typing certain other European languages
>>>   more difficult, is that drawback possibly of greater importance for
>>>   users living in Portugal (Europe)?
>>>
>>> The only Portuguese locales which are supported in Ubuntu are pt_PT and
>>> pt_BR.
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/518056
>>>
>>> Title:
>>>   cedilla appears as accented c (ć instead of ç) when typing 'c
>>>
>>> Status in central project for keyboard configuration:
>>>   Confirmed
>>> Status in gtk+2.0 package in Ubuntu:
>>>   Confirmed
>>> Status in language-selector package in Ubuntu:
>>>   Fix Released
>>> Status in libx11 package in Ubuntu:
>>>   New
>>> Status in xkeyboard-config package in Ubuntu:
>>>   Confirmed
>>>
>>> Bug description:
>>>
>>>   When typing in a US-international keyboard with dead-keys (or
>>> UK-international),
>>>   typing 'c results in an accented c instead of a cedilla.
>>>
>>>   There is a workaround, which is editing the
>>>
>>>   /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules
>>>
>>>   file and changing the line
>>>
>>>   "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
>>>   "az:ca:co:fr:gv:oc:pt:sq:tr:wa"
>>>
>>>   to
>>>
>>>   "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
>>>   "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"
>>>
>>>   (add the 'en' at the end).
>>>
>>>   However, every time some update on this file is applied, one looses
>>> the change,
>>>   and we get back to the accented c. That means having to modify the
>>> file again,
>>>   logout and login.
>>>
>>>   For me this is no problem. But for my brother, mom, dad, etc, it is
>>> always something
>>>   that at least makes me less proud of having convinced them to use
>>> Ubuntu, because
>>>   they don't know what to do each time this happens.
>>>
>>>   I think we really need a configurable keyboard layout, or at least
>>> (and that would
>>>   be very easy), the inclusion of alternate layouts on install that for
>>> the dead-key
>>>   options (as US-deadkey and UK-deakey), alternate layouts as
>>> US-deadkey-cedilla.
>>>
>>>   This change is relevant for at least Portuguese and French.
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+subscriptions
>>>
>>


** Attachment added: "Screenshot_2015-04-03-10-06-00.png"
   https://bugs.launchpad.net/bugs/518056/+attachment/4365093/+files/Screenshot_2015-04-03-10-06-00.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/518056

Title:
  cedilla appears as accented c (ć instead of ç) when typing 'c

Status in central project for keyboard configuration:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in language-selector package in Ubuntu:
  Fix Released
Status in libx11 package in Ubuntu:
  New
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  
  When typing in a US-international keyboard with dead-keys (or UK-international), 
  typing 'c results in an accented c instead of a cedilla.

  There is a workaround, which is editing the

  /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules

  file and changing the line

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa"

  to

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

  (add the 'en' at the end).

  However, every time some update on this file is applied, one looses the change,
  and we get back to the accented c. That means having to modify the file again,
  logout and login.

  For me this is no problem. But for my brother, mom, dad, etc, it is always something
  that at least makes me less proud of having convinced them to use Ubuntu, because
  they don't know what to do each time this happens.

  I think we really need a configurable keyboard layout, or at least (and that would
  be very easy), the inclusion of alternate layouts on install that for the dead-key
  options (as US-deadkey and UK-deakey), alternate layouts as US-deadkey-cedilla.

  This change is relevant for at least Portuguese and French.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+subscriptions