Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion en.txt
Original file line number Diff line number Diff line change
Expand Up @@ -491,6 +491,7 @@ mdlb
meat masseuse
meat spin
meatspin
meecrob
menage a trois
menage-a-trois
menages a trois
Expand Down Expand Up @@ -806,4 +807,4 @@ zippo cat
zippo-cat
zippocat
zoophile
zoophilia
zoophilia
4 changes: 4 additions & 0 deletions src/en.json
Original file line number Diff line number Diff line change
Expand Up @@ -2477,6 +2477,10 @@
"id": "horseshit",
"match": "horseshit|horse-shit|horse shit"
},
{
"id": "meecrob",
"match": "pile of meecrob"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This JSON takes pipe-separated values for the match attribute and will turn those into individual items in the en.txt list; the id attribute value isn't added to the .en.txt list from this though.

Based on your original change to en.txt, this would instead be:

Suggested change
"match": "pile of meecrob"
"match": "meecrob"

Otherwise, if you wanted to see the full match for either/or you could use:

Suggested change
"match": "pile of meecrob"
"match": "meecrob|pile of meecrob"

Though just defining meecrob for the match would probably result in the desired behaviour for most implementations using this list, e.g. piece of meecrob -> piece of *******

},
{
"id": "piece-of-shit",
"match": "piece of shit|pieces of shit"
Expand Down