Leo Bernard

I found a workaround that keeps the original API intact. After generating your API, add the following line to your `core/request.ts` file: ```ts export const HEADERS = Symbol("HEADERS") ``` Then,...

It looks like the placeholders aren't in the right format. This tool works either with ICU/i18next placeholders like `{email}` or with sprintf-style placeholders like `%s`. I could implement a new...

Currently, json-autotranslate doesn't have support for handling this, but you should be able to just run the command multiple times because it will skip the items you already translated :)

I think it has to do with the translation in line 968 in your file. This tool expects translations to be a string instead of a number. Maybe I can...

Ah, the update I pushed was not related to this issue. I think I can take a deeper look at it on Sunday.

Hey @johnfelipe, Unfortunately I haven't found the time to work on this yet. I can't promise a timeframe since the project is just a side project and my weeks are...

JSON Autotranslate supports all languages that DeepL supports. Currently, that's the following: - bg - zh - cs - da - nl - en - et - fi - fr...

Hmm, that's a good question. JSON Autotranslate doesn't have any specific behavior when it comes to plurals. Adding the "_few" and "_many" keys to the English source file could work,...

Yeah, that's a valid concern. Do you have an idea for how JSON Autotranslate could be improved to accomodate for this situation?

Hey @petrchutny, thanks for your feedback! It's awesome to see this tool being used in real-world products! I'm guessing that you're using key-based translation, like: ```json { "SOME_TEXT": "This is...