Will Yoshida

As mentioned in this [discussion](https://github.com/scribe-org/Scribe-Data/issues/14#issuecomment-1299537864), I would be curious to hear thoughts on where the English keyboard now fits into the roadmap. I feel that the need is definitely there...

Gotchu! Thanks - I think that what you shared makes sense, @andrewtavis! :+1: I did notice as well the new issue created for the translation data, https://github.com/scribe-org/Scribe-Data/issues/23. > Another thing...

I can't remember if this is something that we even considered, but could it be possible if we just add the English keyboard, although without a translation option for it?...

> Something we could start on now is the WDQS queries and the Python formatting scripts above? Would you have an interest in looking at those, @wkyoshida? I could give...

Hey @andrewtavis! I was wondering how this feature would eventually work in the back-end side. I know there's the [Scribe-Data](https://github.com/scribe-org/Scribe-Data) repo, which could be used as the download location for...

> when Android gets up and running we'll need something that's platform agnostic :) Completely agree! :+1: > I removed the word "nazi" from all autosuggestions, for instance, as WWII...

Agreed! We can definitely compare both offerings and evaluate. However, whether it ends up being GitHub or Toolforge for the long-term, I am thinking _atm_ perhaps that the GitHub route...

> I think it's safe to say that we cannot do the top two options above without doing the data download process, but then I wanted to check :) Yeah,...

> My assumption was we’d make source language based tables where the word is the key and all the translations are the other column elements? How does this sound? I...

Potentially related to the past completed issue: https://github.com/scribe-org/Scribe-iOS/issues/30