matergi / translo Goto Github PK

Scenario
When the user creates a subscription, a "charge.succeeded" event is triggered, and their token account is recharged

The current behavior:
upon subscription, the user is automatically charged the entered amount again

Expected behavior:
is that upon subscription, it should not be recognized as "charge.succeeded," and the user should be assigned the predefined tokens instead

understand whether it's better in the add language modal, or outside (adding a language section)

ESLint rule

Make sure that when you save, it sets the project to private and rename 'constants translation' to 'terms/glossary'

Background

1. The user creates the project
2. The user imports a list of English keywords
3. The user adds 2 languages (e.g. Italian and Spanish)

Actual wrong behavior

1. The user opens a keyword
2. The user translates it into all languages
3. It gets translated and inserted only in the last language and not in both

Note: The API returns it correctly, so it might be a client-side error.

Correct behavior

1. The user opens a keyword
2. The user translates it into all languages
3. It gets translated into all languages

we could add a language selector in the settings.
add some languages for the landing page and app.
also create the website sitemap.

https://docs.stripe.com/billing/subscriptions/usage-based

also create the website sitemap

On the page with all keywords, place the translation in the native language below the keyword

Scenario:
When the user attempts to register but does not confirm the email, it does not allow re-registration with the same email

The current behavior:

• The user tries to register but doesn't confirm the email
• The user tries to register again and returns an error

Expected behavior:

• The user tries to register but doesn't confirm the email
• The user tries to register again and confirms the email
• The user tries to register again and returns an error

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

• chore(deps): update dependency @types/node to v22.5.5
• chore(deps): update dependency postcss to v8.4.47
• chore(deps): update nextjs monorepo to v14.2.11 (eslint-config-next, next)
• fix(deps): update dependency @tanstack/react-query to v5.56.2
• fix(deps): update dependency openai to v4.61.0
• fix(deps): update dependency stripe to v16.11.0

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency eslint-plugin-react to v7.36.1
• fix(deps): update dependency lucide-react to v0.441.0
• fix(deps): update dependency concurrently to v9
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#react-render-errors-in-app-router

To test when the user cancels the subscription and recreates it the following month, to see if it recharges them with additional tokens

It might be convenient to enable the display of only untranslated keywords (as a filter) to immediately see those that still need to be translated in a particular language

The database structure is already prepared; we need to work on the UI interface

prompt example:

Sto lavorando alla internazionalizzazione della mia applicazione. Vorrei tradurre il testo alla fine di questo messaggio, utilizzato in questo contesto: "{{keyword.context}}".
Potresti scrivermi le traduzioni in {{i18n.languages}}? 
[[La traduzione deve essere informale]] <-- {{settings.audience}}
[[nel tono di un sito web tecnologico]] <-- {{settings.description}}
[[Il pubblico di riferimento è sia maschile che femminile]] <-- {{setting.gender}}
con un'età compresa tra i {{settings.ageFrom}} e i {{settings.ageTo}} anni. 

ricorda che “Fotogramma” si traduce così:
"it": "Fotogramma",
"en": "Frame",
"es": "Fotograma",

Genera un JSON unico in questo modo:
{
    "en": "",
    "it": "",
    "es": ""
}

dove:
language-id per inglese = en
language-id per italiano = it
language-id per spagnolo = es
...

To achieve a well-done translation, we need to provide context to the AI, and we do this through project variables

• Brief project description
• Formality
  • Formal
  • Informal
  • Neutral
• Target audience
  • Male
  • Female
  • Other
• Target audience age
• Words designated as constant translations
  • example: "Subscription" -> "Abbonamenti", no "iscrizione"