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

Dictionnaries #91

Closed
kotecky opened this issue Apr 27, 2020 · 23 comments
Closed

Dictionnaries #91

kotecky opened this issue Apr 27, 2020 · 23 comments

Comments

@kotecky
Copy link

kotecky commented Apr 27, 2020

Does anything prevent the project to reuse the dictionaries used by other projects? E.g. https://github.com/LineageOS/android_packages_inputmethods_LatinIME/tree/lineage-17.1/dictionaries

@sandsturm
Copy link
Contributor

I don't think so. The structure is the same. It is just a matter to generate/add the dictionaries to the repository. Do we want to add them to openboard source code, should I do it?

@roshavagarga
Copy link

The LineageOS dictionaries are more or less AOSP ones with some improvements here and there. As long as you keep the original authors I'd say it's productive to have them as long as they are superior to the ones we have, wherever there's an overlap. I would suggest some reciprocity by also opening merges of openboard dictionaries to LOS through https://review.lineageos.org

@sandsturm
Copy link
Contributor

@roshavagarga
Copy link

Definitely, but I believe a few of the other dict patches are modifications on top of that. The abandoned merges you linked are actually mine - I gave up on figuring out git just to upload 2 files to gerrit.

@kotecky
Copy link
Author

kotecky commented Apr 28, 2020

@sandsturm

But even LineageOS sources it from Google.

I wrote the initial comment from a user's perspective. As such i would not mind using a dictionary sourced from Google provided it contains no tracking binaries or similar.

@sandsturm
Copy link
Contributor

But did they ever update the dictionaries? The sources from Google and LineageOS are quite old, the last commit is 3 or 4 years old. Should we take them as the basis and add our own list of words in another file or fork them in the openboard repositories? In #83 I extended the original dictionary with words I missed and added them back to the repository.

@dslul, what your opinion here?

@roshavagarga
Copy link

LineageOS uses the AOSP dictionaries as bases - some are improved, others aren't, without checking their gerrit there's no way to know what's been improved and what hasn't. I'm not sure whether openboard uses these as its basis, but if it does, any improvements to those can be forked over to LOS too and vice versa. In cases where they differ, there's no way to know which one is better without a user's input.

@sandsturm
Copy link
Contributor

I have now added the de dictionary change to the Android sources: https://android-review.googlesource.com/c/platform/packages/inputmethods/LatinIME/+/1298694

My favorite solution would be to use the Android repositories as the golden source.

@roshavagarga
Copy link

Cool. I suggest also sending that in the LineageOS gerrit, as AOSP rarely if ever accepts any changes to its AOSP keyboard, since they have entirely transitioned to the proprietary GBoard.

@sandsturm
Copy link
Contributor

With pleasure. Should I wait until the change is approved by Google, or should I already make the change in LineageOS?

@roshavagarga
Copy link

Definitely don't wait. I'd wager your change will never get a response, let alone approval by Google. Just make sure authorship and whatnot is preserved.

@sandsturm
Copy link
Contributor

@roshavagarga
Copy link

Changes are only reviewed and merged through their gerrit, available at https://review.lineageos.org/.

@sandsturm
Copy link
Contributor

Tried to get around gerrit, but ok. https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/274373

@roshavagarga
Copy link

@sandsturm Check the link, 2 comments you need to address and it'll be on the fast track for merging :)

@malekairmaroc7
Copy link

You can maybe add dictionary update server?

@sandsturm
Copy link
Contributor

Is your question, when a new version is published which includes the dictionary?

@malekairmaroc7
Copy link

Is your question related to me @sandsturm ?

@sandsturm
Copy link
Contributor

Yes :-)

@malekairmaroc7
Copy link

malekairmaroc7 commented May 27, 2020

Oh then, yes that's what I mean but through the app of course😁

@sandsturm
Copy link
Contributor

Ah, yes. @dslul needs to do this ;-)

@malekairmaroc7
Copy link

yeah sure. @dslul 🤓😝😁

@dslul
Copy link
Member

dslul commented Sep 7, 2020

Is your question, when a new version is published which includes the dictionary?

Before the end of this month!

@dslul dslul closed this as completed Sep 7, 2020
lukaszgdula6 pushed a commit to lukaszgdula6/openboard that referenced this issue Dec 21, 2020
Minor changes to MIUI Warning & Hebrew translation for new strings
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

5 participants