-
Hi, I'm interested in your project and want to have some contribution on it. After reading the Contributing.md, I want to improve some points relating to contents and its heading structure to make it …
-
- User is unable to set up formality in default settings:
- Add a note which MT providers do or do not support formality and in which languages.
-
| Metadata | |
| -------- | --- |
| Owner(s) | @nikomatsakis |
| Team(s) | [types](https://github.com/rust-lang/types-team) |
| Goal document | [2024h2/a-mir-formality](https://r…
-
### Extension
https://www.raycast.com/mooxl/deepcast
### Description
DeepL allows specifying formality in the API request. It would be great to add support for this parameter
### Who will be…
-
So now that we have our repo (🎉!), let's decide on some formal rules before we get into translating áll the stuff. Deciding on and documenting them should hopefully make both the processes now as well…
-
"Formality" parameter is needed to force formal/informal language, which important in some locales like es_ES
Reference:
https://www.deepl.com/docs-api/translate-text
-
Hi there,I have some questions to ask.
1. Is the "form_em" folder used to run formal transfer code?
2. If I use "form_em" to run yelp dataset, should I get sentiment transfer result or form transfer…
poang updated
2 years ago
-
**Feature description**
- Warrant Board from MRP, but remade.
**Specification**
Already finished, ticket only exists as a formality until it's uploaded.
-
Port 1 [a-mir-formality](https://github.com/rust-lang/a-mir-formality) crate to use StableMIR APIs.
This will help us assess our APIs with a real use case.
-
This causes way to many issues, we need to find a good way to mitigate the repos being outdated; while still being able to live test if needed. I have had to many issues with repos not linking correct…