Skip to content

Conversation

@bountonw
Copy link
Owner

No description provided.

Ideally, these should be comma delimited 3 column files with
`bad_term, good_term, comment` or `bad_term, , comment`
@bountonw
Copy link
Owner Author

@mattleff

Since I am focused on catching up with translation and editing, issues regarding linting of the translation files has been front and center. I am also in the process of importing some Lao text that someone else did and there are dozens of issues in this short file. Having spelling linting for forbidden and flagged terms will help in this process as more people work on the files.

I have created two placeholder files for words that although spelled correctly, should raise a warning flag. in order to see in context if we really want those words or not.

Ideally, these should be comma delimited 3 column files with bad_term, good_term, comment or bad_term, , comment. I have not added the columns yet so as not to add another layer of complexity until you are ready for it.

Can you set these files to check on their respective languages but not to block merging, only to raise warning flags. (If we do have 3 columns, ideally, the warning flag would include the suggested good word and comment.)

@bountonw
Copy link
Owner Author

These lintings should run on all of their respective *.md files regardless of status. A spelling error fixed at the raw stage is an edit that doesn't need to be made later.

Add เจา 

Possibly a typo for เขา, but could be part of the Thai word เจาะ
@bountonw bountonw self-assigned this Mar 12, 2024
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