Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mapping problem in keyboard-apu from 48-key to Brazilian 47-key layout #1

Open
rueter opened this issue Feb 21, 2024 · 7 comments
Open
Assignees

Comments

@rueter
Copy link
Member

rueter commented Feb 21, 2024

The Apurinã keyboard should have tilde combinations for all vowels and a modifier letter apostrophe to mark glottal stop. In addition we want circumflex, grave, acute and diaereses.

This äëïöüÿ ãẽĩõũỹ àèìòùỳ áéíóúý works on my M2, Sonoma 14.3.1 in Finland, but it does not quite map to the Brazilian Mac Air used by Sidney Facundes, hence a distinction in the names apu_FI and apu_BR.
Note, for example, that the FI-board shows both sides of the square brackets in the QWERTY row, but the BR-board moves the right-hand bracket to the beginning of the next line.
Please, ask for additional information.

apu_BR_Divvun_default
apu_BR_Divvun_shift
apu_BR_Divvun_alt_shift
apu_BR_Divvun_alt
apu_FI_Divvun_default
apu_FI_Divvun_shift
apu_FI_Divvun_alt
apu_FI_Divvun_alt_shift

@rueter
Copy link
Member Author

rueter commented Feb 21, 2024

The por_BR board looks like this:
por_BR_default
por_BR_shift
por_BR_alt_shift
por_BR_alt

@snomos
Copy link
Member

snomos commented Feb 27, 2024

I edited the layout file to be identical to Apple's Brasilian Portuguese, as it appears on my computer, using an ISO keyboard.

Cf 190b7bc

It should produce all the accented vowels you desire, although the deadkeys are in different positions.

I did this for two reasons:

  • I think it is wise to deviate as little as possible from the regular Brasilian keyboard as possible
  • I want to debug our keyboard build process:
    • if the kbdgen tool is working correctly, then this version should look exactly as the por_BR keyboard above. If not, we have a known state to debug from, with no other changes than those produced by kbdgen

Do NOT change any deadkeys or anything else, just build this new version, and give it to Sidney, and ask him to take screen shots so that we can compare.

@rueter
Copy link
Member Author

rueter commented Feb 27, 2024

Now, there is only one difference observed in the layout.
On the por_BR keyboard tilde requires +shift ( see below).
Otherwise, the keyboard looks right and seems to work right.

apu_Divvun_01_default
apu_Divvun_02_shift
apu_Divvun_03_alt
apu_Divvun_04_alt_shift
apu_Divvun_05_comb_view
por_BR_shift_for_tilde

@snomos
Copy link
Member

snomos commented Feb 27, 2024

Now, there is only one difference observed in the layout.
On the por_BR keyboard tilde requires +shift ( see below).
Otherwise, the keyboard looks right and seems to work right.

This is how it is on the Apple Brazilian keyboard. I want it to be identical with that one, and make sure it works everywhere the correct way before we start to change anything. And from the screen shots, it does not look like shift is required to get tilde.

On the other hand, it seems that the screen shots are not from the latest version that I pushed to GitHub, it contains deadkeys that I removed. Could you make sure that the version of the keyboard package is 0.1.1, not 0.1.0?

Whose computer are the screen shots from? It seems to be a Mac with an ANSI keyboard?

@rueter
Copy link
Member Author

rueter commented Feb 27, 2024

These pictures all come from Sidney's Mac Air.
Sidney says the shift for Tilde is standard.

@rueter
Copy link
Member Author

rueter commented Feb 28, 2024

Unable to generate macos version on own mac.
Have removed and reinstalled giellalt, and cloned
Still get:

"/Users/jackrueter/Dropbox/Github/giellalt/keyboard-apu/apu.kbdgen"
thread 'main' panicked at src/build/macos/generate_macos.rs:486:25:
dead key `"` in target list but not the transforms.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
make: *** [Makefile:604: mac] Error 101

Maybe you haven't pushed everything onto Github.
see also:

Github Bot: Check [Build keyboard: macos-latest - keyboard-apu](https://github.com/giellalt/keyboard-apu/runs/22033224856) completed (failure). ([b8aacd210c4](https://github.com/giellalt/keyboard-apu/commit/b8aacd210c4f77c029493e77e9ca933eab91cf9a))

Github Bot: Check [Build keyboard: windows-latest - keyboard-apu](https://github.com/giellalt/keyboard-apu/runs/22033225532) completed (failure). ([b8aacd210c4](https://github.com/giellalt/keyboard-apu/commit/b8aacd210c4f77c029493e77e9ca933eab91cf9a))

both have failed, with no push since

@snomos
Copy link
Member

snomos commented Feb 28, 2024

Unable to generate macos version on own mac.

Sorry, my bad. I have fixed it, and also replaced the Sámi flag with the UN flag. New version is 0.1.2, and it has already built successfully for Mac, and is available in Divvun Manager.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants