‘Translate “card” as “diapositivo” in the Portuguese version, especially when exporting to PowerPoint.’

“Slide” is also used, but never ‘cartão’.

By the way, you should give me a bonus for the suggestion :-)

Not really a feature request, more like a small bug. When you translated the word "Present", i.e "I want to start presenting this Gamma", it was translated to the Hebrew word of "הווה", which means present=the present time. It should be "הצג". See screenshot :)

Hi Gamma team! I create many Gammas in Esperanto, but Esperanto isn’t available as a selectable output language in the app. Because of that, Gamma often:

generates content in my currently selected language instead of Esperanto,

produces mixed-language output, and

Esperanto translation/rewrite quality is inconsistent (likely because Esperanto isn’t treated as a first-class “lead” language).

Images / text-in-image issue

I also generate images in Gamma that contain text in Esperanto (e.g., posters, titles, educational graphics). The image model frequently corrupts Esperanto diacritics or replaces them with incorrect characters. This breaks essential letters: ĉ ĝ ĥ ĵ ŝ ŭ (including both uppercase and lowercase), making the visuals unusable.

What I need / proposal

Add Esperanto (eo) to the language selection for AI generation (any “Output language” dropdown in the UI).

Add an option like “Keep language fixed” / language lock, so Gamma doesn’t auto-switch output into the UI language.

Ensure Esperanto text keeps correct diacritics (ĉ ĝ ĥ ĵ ŝ ŭ) across generate, rewrite, expand, summarize, and regenerate.

Improve language detection: if the prompt is in Esperanto, the output should stay in Esperanto by default.

For images with text, preserve Esperanto diacritics reliably (no missing hats/breves, no substitutions, no random degradation between regenerations).

Why it matters

Esperanto has an active international community and is widely used for education and cross-border communication.

For users who work in Esperanto, language drift and broken diacritics create extra editing time and cause errors in published materials.

Adding Esperanto would unlock a meaningful new creator segment for Gamma.

Community distribution

If Esperanto becomes a selectable output language in Gamma, I will gladly share and promote this capability internationally within the Esperanto community (teachers, content creators, local associations), because it removes a major barrier for producing high-quality Esperanto materials.

Acceptance criteria (simple tests)

I can select Esperanto (eo) as output language.

A Gamma generated from an Esperanto prompt stays fully in Esperanto across regenerate/rewrite.

No automatic switching to the UI language unless I choose it.

Diacritics remain correct after edits (ĉ ĝ ĥ ĵ ŝ ŭ, upper/lowercase).

When generating an image with Esperanto text, diacritics render correctly and consistently, and don’t degrade on regeneration.

The language Presenting in the slides differs from the specified language and also not accurate in presenting the slides. worest spelling in Telugu indian language. It needs to be corrected. Some times the matter needs to be corrected hence it will be better to provide edit facility.

While editing a RTL presentation, and adding a text which start with LTR input, the line will automatically be aligned to the left, with no option for manual configuration.

This creates issues when trying to add English inside my RTL text.

In the Hebrew language, when aligned from right to left, the punctuation marks do not align. Likewise, if you combine Hebrew and English together, the alignment is also not done as required. Therefore, currently in the Hebrew language, to achieve correct visibility, I constantly use center alignment and lower punctuation marks at the end of lines. Also, when you press Enter to lower a line, it decreases by the size of a paragraph and not by one line.

M'agradaria que el català sigui un idioma disponible a la vostra interfície

Commands, action buttons, and other text in the interface are translated very unnaturally. Most begin with the word "Please..."—no one in Poland says that, unless they're addressing another person and asking them to do something. Nor, in any computer program, does any command begin with the word "please."

The way how interface and localization to polish looks like I will give you some examles:

Instead of command "Add" it is "Please add", instead of "Edit theme" it is "Please edit theme" - sounds stupid isn't it?

I beg you - CHANGE IT.

I can help you with that if you send me localization file (translation) like english=>polish I can adjust polsih words to be like they suppose to be - free of charge. It is just annoying how it sounds right now.

There is no support for Georgian "ქართული" language, please add it as there are people that wish to use it from Georgia but can't due to the website not supporting it.