A community-generated conlang dictionary system for minimalist languages that make heavy use of compound phrases.
Find out how other Hîsyêô speakers are saying complicated English terms. The search also looks for related terms to try to help you find a suitable translation fast.
Community members can add new terms, translations and votes for existing translations and they get processed through a Pull Request to this project's code repository.
You can view translation text in either the Latin, Abugida, or Syllabary scripts. Note that this doesn't work for translation entry, only Latin is supported for submitting new translations because the gramamr checker currently only works for the Latin script.
Votes can be provided to indicate which is the best overall, most succinct, most specific, and funniest translations.
To add new content, you must provide a verification method and a moderator will personally reach out to you to verify the validity of your entries.
No data is locked in a database. The entries and votes are exposed directly for consumption by other services.
Due to Hîsyêô's strict orthography, a word/syllable encoding was built to reduce translation submission size by at least 50% which increases the maximum submission size.
This is a Next.js project bootstrapped with create-next-app.
- Add a guard client side that replaces a vote if the user changes to a different translation for the same category
- Add a reddit username authentication
- Add a synonyms library that searches for alternatives
- When in a term detail page, search for any closely related words using synonyms and offer them to the user to navigate to
- Show a count of how many translations have been written for the suggested alternative terms
- Add noun phrase grammar checking before submission is allowed
- Allow switching between latin, abugida and syllabary Hîsyêô text
- Make the main rendering view into a window that only renders html within proximity of user's scroll location (when list of terms gets big)
- Add a warning toast to indicate that user's prior selection was unset
- Allow the user to see newly added translations in the term detail page before they are submitted
- Add a way to click on a submission queue item and navigate to that new term, new translation or voted translation
- Make submitter not a field for submission entries because of the submission author
- Add a ui change when the screen resolution is small: "English → Hisyeo" is removed, "X items translated" just becomes "X" and the "untranslated" label is removed ôêîû
- Make "No username to validate" error only appear once
- Get untranslated page working again and with grammar checking
- Add a button in the header that takes you right to the PRs for the repo
- Add link to submission files from translation entries in term detail pages
- Make the untranslated button clickable on all screens that it's viewable on
- Fix style outlines for terms that contain pending votes and entries
- Fix for adaptive display of best translations (only show 2 sections if only 2 have top translations)
- Show search results in order of levenstein distance from the search param
- Fix for proper name HTF-INT encoding/decoding
- Add a sort dropdown button on term detail to sort translations by each vote category
- Allow user to add translation immediately upon adding a new term
- When clicking modify, only copy the latin text up into the new translation field
- Add a new JSON file for storing user merges and when aggregate script runs, it checks names against this JSON file and replaces them when they have a merge record present
First, set your github repo in .env.local:
NEXT_PUBLIC_GITHUB_REPO_URL=https://path.to/repoThen run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun devOpen http://localhost:3000 with your browser to see the result.