Proof of concept for using langid - #1
Open
ojas-uls-dev wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Not really a pull request, but just wanted your eyes on this.
As discussed in weekly one on one, here is one way we could detect English used within our XML. The approach is to take sequences of 5 words (skipping 3 at a time) and classify small phrases into english. The task of classifying small phrases is done by langid, a small classification model that does this task pretty quickly.
Langid is largely abandoned (last commit was 9 years ago) however is functional enough for us to make use of it. It was able to process a wikipedia page worth of phrases in a couple seconds on laptop hardware, so fast enough that we aren't waiting for days to process all our documents.