Skip to content

Conversation

@10Develops
Copy link

@10Develops 10Develops commented Apr 27, 2025

Armenian and Cyrillic layouts were changed by following way.

  • Removed the former Armenian phonetic layout, replacing with a one used in actual typewriters (ՔՎԸՐՏՃ).
  • Added the real Armenian typewriter layout (ՃՓԲՍՄՈ).
  • Added traditional (pre-revolution) Russian layout (ЙІУКЕН).
  • Improved modern Russian layout according to GOST 6431-90 (ЙЦУКЕН).
  • Added Russian phonetic layout (ЯВЕРТЫ).

Note: Armenian symbols on Unicode (also formerly on ArmSCII) as "․" (U+2024) and "։" (U+0589) are different from normal "." (U+002E) and ":" (U+003A). Thus the last two were also added on lower section, to make proper experience as navigation on Armenian language domains.

If needed, addition of another layouts are possible, such as Dvorak-style.

@@ -1,42 +1,42 @@
<?xml version="1.0" encoding="utf-8"?>
<keyboard name="ЙЦУКЕН (Русский)" script="cyrillic">
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@carrot-cookie and @Thunder-Squirrel, you edited this layout in the past, what do you think of these changes ?

@@ -0,0 +1,44 @@
<?xml version="1.0" encoding="utc-8"?>
<keyboard name="ЙІУКЕН" script="cyrillic">
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This layout has very narrow keys:
shot

I think it would be more practical to type on if some letters were moved to the side of other letters. Do you think that would make sense ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, actually this was the original layout:

JIUKEN_typewriter

Very hard to determinate which row some keys should go. This variant seems proper, but need to know that this layout is an experimental anyway.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The typewriter in the picture has 11 columns while the layout you propose has 13. It seems that your layout has more letters on it ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was one missing key on this layout, it's added later. Now it has the same amount of keys as on this picture. Both have 34 keys now.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be like in the picture, з and х should be one row up, after щ. ц and э should be elsewhere entirely, perhaps in the corners.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, the bottom row is getting larger, making the keys even smaller. I suggest moving some keys, perhaps putting Shift on the second row ?

10Develops and others added 2 commits May 12, 2025 03:58
Letter б was missed, adding.
Copy link
Owner

@Julow Julow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here are some warnings generated by the script:

armn_cpbsmo: Duplicate keys: չ
armn_cpbsmo: Layout includes some ASCII punctuation but not all, missing: !, ", #, $, %, &, ', *, +, <, =, >, ?, @, [, ], ^, `, {, }, ~
armn_kvertc: Layout includes some ASCII punctuation but not all, missing: !, ", #, $, %, &, ', *, +, <, =, >, ?, @, [, ], ^, `, {, }, ~
cyrl_jcuken_ru: Layout includes some ASCII punctuation but not all, missing: #, $, &, ', *, <, >, @, [, ], ^, `, {, }, ~
cyrl_jiuken: Layout includes some ASCII punctuation but not all, missing: #, $, &, ', *, +, <, =, >, @, [, ], ^, _, `, {, }, ~
cyrl_yaverti: Layout includes some ASCII punctuation but not all, missing: ~
cyrl_yawerty: Layout includes some ASCII punctuation but not all, missing: #, $, &, ', *, <, >, @, [, ], ^, `, {, }, ~

I guess the lack of ASCII punctuations is on purpose ? In that case only the warnings in armn_cpbsmo and cyrl_yaverti make sense.

@Julow
Copy link
Owner

Julow commented May 22, 2025

@rafasaurus You added the previous Armenian layout in #490
What do you think of the two new Armenian layouts ?

@rafasaurus
Copy link
Contributor

let me build and test, will follow up

@10Develops
Copy link
Author

10Develops commented May 24, 2025

Here are some warnings generated by the script:

armn_cpbsmo: Duplicate keys: չ
armn_cpbsmo: Layout includes some ASCII punctuation but not all, missing: !, ", #, $, %, &, ', *, +, <, =, >, ?, @, [, ], ^, `, {, }, ~
armn_kvertc: Layout includes some ASCII punctuation but not all, missing: !, ", #, $, %, &, ', *, +, <, =, >, ?, @, [, ], ^, `, {, }, ~
cyrl_jcuken_ru: Layout includes some ASCII punctuation but not all, missing: #, $, &, ', *, <, >, @, [, ], ^, `, {, }, ~
cyrl_jiuken: Layout includes some ASCII punctuation but not all, missing: #, $, &, ', *, +, <, =, >, @, [, ], ^, _, `, {, }, ~
cyrl_yaverti: Layout includes some ASCII punctuation but not all, missing: ~
cyrl_yawerty: Layout includes some ASCII punctuation but not all, missing: #, $, &, ', *, <, >, @, [, ], ^, `, {, }, ~

I guess the lack of ASCII punctuations is on purpose ? In that case only the warnings in armn_cpbsmo and cyrl_yaverti make sense.

Yes. These symbols appearing only on English and other Latin layouts. So not very great idea to overload Russian and Armenian layouts with these symbols. The symbols appeared are the most identical to what was using on actual layouts, as English one has f.e..

@Julow
Copy link
Owner

Julow commented Jul 11, 2025

I would like to merge this but because you do a lot of things in the same PR, it's hard to review and discuss with other users.
Could you propose the new layouts in a separate PR from the changes to existing layouts ?

@10Develops
Copy link
Author

I would like to merge this but because you do a lot of things in the same PR, it's hard to review and discuss with other users. Could you propose the new layouts in a separate PR from the changes to existing layouts ?

What is hard to review? Every change is explainable, just need to purify.

@Julow
Copy link
Owner

Julow commented Jul 22, 2025

What is hard to review?

Other contributors might want to have a look at your modifications to the existing layouts but it's not easy because your PR also add several layouts. I suggest that you open a new PR with the added layouts only, so that it can be merged quickly.

@10Develops
Copy link
Author

What is hard to review?

Other contributors might want to have a look at your modifications to the existing layouts but it's not easy because your PR also add several layouts. I suggest that you open a new PR with the added layouts only, so that it can be merged quickly.

You mean the removed/edited layouts would be here?

@Julow
Copy link
Owner

Julow commented Aug 31, 2025

You mean the removed/edited layouts would be here?

Yes.

@10Develops
Copy link
Author

You mean the removed/edited layouts would be here?

Yes.

So a branch for added keyboards was created, so there would be all added layouts, and edited/removed ones would be here.

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

Successfully merging this pull request may close these issues.

3 participants