Fixed Point Translations for websites.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
So, I'll first define Cyclic Translations.
Basically for some languages `A` and `B` we can apply two mappings (Google Translate):
```
G1: LanguageA -> LanguageB
G2: LanguageB -> LanguageA
```
Then consider the composition, `G3 = G1 o G2 : LanguageA -> LanguageA`. Then suppose that `G3` has a local fixed point in `LanguageA`.
Basically convert all the text on a page to `lim n-> infinity G3^n(text: LanguageA)`
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files, tests, or entry points are named. Start by clarifying the intended website scope and how the Google Translate mappings should be applied, then define what convergence and completion mean for page text.
Written by the indexing model from the issue text.
Assessment
- Domain
- localization, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100