i18n / multilingual content
Open
backlog
- Dominant language
- CSS
- Stars
- 1
- Forks
- 0
- Avg merge
- 26m
- Merged PRs (30d)
- 62
Description
From LATER.md: i18n / multilingual content — watch for demand. Both search engines are per-language-capable (the cherry engine's tokenizer and stopwords are English-only today; Pagefind is zero-config multilingual). No design yet; this issue collects demand and use cases.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with LATER.md and collect concrete multilingual demand and use cases. Then inspect the cherry engine's tokenizer and stopword behavior alongside Pagefind's multilingual support. This issue is complete only when a design and scoped requirements are agreed; the payload does not define them yet.
Written by the indexing model from the issue text.
Assessment
- Domain
- internationalization, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100