Regular Expressions 101

Community Patterns

1

ตรวจสอบพยัญชนะต้นตัวสะกดสระและวรรณยุกต์ไทย

Created·2026-01-22 01:36
Updated·2026-01-23 12:42
Flavor·JavaScript
ตรวจสอบพยัญชนะต้น (ต้องมี) ตรวจตัวสะกดสำหรับสระที่ต้องมี ตรวจสอบการวางสระและวรรณยุกต์ไทย หมายเหตุ การตรวจสอบตัวสะกดในภาษาไทยตรวจสอบได้ยากเพราะภาษาไทยเป็นภาษาที่เขียนติด ๆ กันไม่มีการแบ่งคำอย่างชัดเจนทำให้การอ่านภาษาไทยผู้อ่านต้องใช้ความหมายของคำในการตัดสินการอ่านแบ่งคำตามความเหมาะสมเช่นคำว่า "ตากลม" อาจอ่านเป็น "ตาก-ลม" ก็ได้ หรืออ่านเป็น "ตา-กลม"ก็ได้ ดังนั้นการเขียน Regex เพื่อทำการตรวจสอบอาจช่วยได้ระดับหนึ่ง อ่าจมีผิดบ้างถูกบ้าง แต่ก็ถือว่าเป็นเครื่องมือที่ใช้ช่วยเหลือในการตรวจสอบเพิ่มเติมได้ 80% ของความเป็นไปใด้ก็แล้วกันนะครับ หวังว่าการเขียนเพิ่มเติมส่วนนี้ จะมีประโยชน์บ้างไม่มากก็น้อย
Submitted by อธิปัตย์ ล้อวงศ์งาม
1

Regex for Matching Documentation Websites

Created·2024-11-24 01:45
Flavor·JavaScript
Regex for Matching Documentation Websites This repository contains a powerful regular expression designed to match URLs that commonly point to documentation-related websites. The regex is optimized for flexibility, covering various terms and URL patterns. Regex Pattern ^.(?:\.|\/)(docs|documentation|help|guide|manual|reference|api|kb|support|resources|wiki|developer|how-to|tutorials|examples|learn|instructions)(?:\.|\/)?.$ Purpose This regex is intended to identify URLs that contain keywords associated with documentation or support websites. It handles common patterns in subdomains, directories, and file paths. Explanation ^.*: Matches any characters at the beginning of the URL (any prefix). (?:\.|\/): Matches either a period (.) or a forward slash (/) preceding the keyword. (docs|documentation|help|guide|manual|...): Matches any of the keywords listed in the group. (?:\.|\/)?: Allows an optional period (.) or forward slash (/) following the keyword. .*$: Matches any characters following the keyword (any suffix). Examples Positive Examples The following URLs should match the regex: https://example.com/docs http://docs.example.com https://example.com/documentation https://sub.domain.com/docs/index.html https://example.com/help https://api.example.com/docs http://example.com/manual/index.html https://wiki.example.com http://developer.example.com/guide https://example.com/tutorials/docs/page https://kb.example.com/docs/tutorial.html https://example.com/resources/documentation/tutorial.html http://example.com/reference/help/documentation.html https://developer.example.com/docs/tutorials/index.html http://support.example.com/documentation/overview https://resources.example.com/docs/v1/tutorial https://example.com/how-to/documentation http://example.com/api/reference/docs https://example.com/reference/v2/index.html http://example.com/docs/resources/api.html Negative Examples The following URLs should not match the regex: https://example.com/documentary http://helpful.example.com https://manuals.example.com http://example.com/references https://example.com/resourceful http://example.com/wiki-books https://apiary.example.com http://example.com/documents http://example.com/documentable https://help-center.example.com http://manual.example.com/docsystem https://example.com/resourcesful http://api.example.comary https://example.net/instructions-v1 http://example.org/learned-tutorial http://example.com/support-center Author Jeremy Georges-Filteau Website Github
Submitted by jgeofil

Community Library Entry

1

Regular Expression
Created·2023-01-09 15:47
Updated·2023-01-09 15:48
Flavor·Java

"
^ # get the title of this movie or series (?<title> [-\w'\"]+ # match separator to later replace into correct title (?<separator> [\s.] ) # note this must be lazy for the engine to work ltr not rtl (?: [-\w'\"]+\2 )*? )(?: # if this is an episode, lets match the season # number one way or another. if not, the year of the movie # make sure this is not just a number in the title followed by our separator. # like, iron man 3 2013 or my.fictional.24.series (?! \d+ \2 ) # now try to match the season number (?: s (?: \2? )? )? (?<season> \d\d? ) (?: e|x (?:\2? )? ) (?<episode> \d\d? ) # needed to validate the last token is a dot, or whatever. (?: e\d\d? (?:-e?\d\d?)? | x\d\d? )? | # this is likely a movie, match the year [(\[]?(?<year>\d{4})[)\]]? ) | # optional release name (?:(?<release> PROPER | REPACK | LIMITED | EXTENDED | INTERNAL | NEW(?:\ SOURCE)? | NUKED | UNRATED | .*?\ EDITION | HC)) | # optional resolution group (?<resolution> \d{3,4}\ ?p) | # optional quality group (?<quality> HDTV | WEB[-.]?DL | HDDVD | DVDRip | DVD | B[DR]Rip | Blu[-.\ ]?Ray | HDRip | WEBRIP ) | # optional codec group (?<codec> XviD | X26[45] | h26[45] | hevc ) | # optional audio group (?<audio> AC3 | AAC | DTS | DD5\.1) | # optional team group with hyphen prefix (?:-(?<team>.*?))? # optional extension group with . prefix (?:\.(?<extension>mkv|avi|mp4|srt))? $
"
gmix
Open regex in editor

Description

Analyze whether the torrent name is a Movie or TV Episode

Inspired from https://regex101.com/library/yP4bY4 There is two versions, see differences at the bottom

Groups:

  • Title (of the Movie/of the TV Series)
  • Season (if TV Episode)
  • Episode (if TV Episode)
  • Year (if Movie)
  • Name (only in v1, should match the TV Episode title if present)
  • Release name (PROPER, REPACK, LIMITED, etc..)
  • Resolution (720p, 1080p, etc..)
  • Quality (HDTV, BluRay, WebRip, etc..)
  • Codec (Xvid, x265, x264, etc..)
  • Audio coding (AAC, AC3, DTS, etc...)
  • Team (torrent group/team)
  • Extension (mkv, avi, mp4, etc...)

Versions:

  • v1, include the TV Episode title, and have all the groups in a single match, but will misinterpret the "name" and "team" groups if the expected pattern is not respected (see in the test strings/regex rules)
  • v2, does not include "name" group but is more reliable, will ignore unexpected patterns.
Submitted by Hot Priest