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

Show dictionary on add translation #1084

Merged

Conversation

Elktro
Copy link
Contributor

@Elktro Elktro commented Aug 7, 2019

When adding new or checking existing stroke, the add translation dialog did not show in which dictionary mapped entries belong to.

On the add translation dialog, the mapping information on the stokes written to the "Strokes" text box will now show the dictionary in which the currently used mapping is defined as well as other mappings found in other dictionaries. This also fixes bug in which filtering from one dictionary mapping prevented other mappings to be used from other dictionaries.

Elktro added 4 commits August 6, 2019 18:48
When adding new or checking existing stroke, definitions the dialog
box shows also the dictionary file name excluding the path of the
current mapping if exists. It also lists other mappings if present
in other dictionaries.

Translation text style is changed to bold for better visiblity.
Added tests for lookup_from_all. A bug was also found in the filtering of
key value pairs in the dictionary collection lookup-function that was not
picked up by the tests due to wrong assertion. If a value was fitterred out
from one dictionary, no other value were returned even if a value that is
not supposed to be filtered out appears in a different dictionary.

The filtering is now fixed.
@morinted
Copy link
Member

morinted commented Apr 3, 2020

I'm excited about this PR! Some screenshots

Before:

Screen Shot 2020-04-03 at 11 04 01 AM

After:

Screen Shot 2020-04-03 at 10 33 14 AM


Struggling with the "It is also mapped to:" sentence, wondering if we should consider something like…

  • "Other dictionaries:"
  • "Masked entries:"

Do we want to consider a different format, too? Something with less English:

PWHERP:
• blerp custom.json (Active)
• blerpoo personal.json
• blerp main.json

With the dictionary text color maybe a gray so that the translations stand out.

@morinted
Copy link
Member

morinted commented Apr 5, 2020

My previous screenshots didn't include the bold font present in the PR

Screen Shot 2020-04-05 at 7 33 16 PM

@morinted
Copy link
Member

I made my suggested changes, the result is
Screen Shot 2020-10-14 at 2 24 10 PM

@morinted morinted merged commit 9f1bdde into openstenoproject:master Oct 14, 2020
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.

2 participants