Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to use STRING1 or anyother non standard modifiers in translations #29

Closed
Aswn opened this issue Oct 18, 2020 · 4 comments
Closed

Unable to use STRING1 or anyother non standard modifiers in translations #29

Aswn opened this issue Oct 18, 2020 · 4 comments
Labels
enhancement good first issue

Comments

@Aswn
Copy link

@Aswn Aswn commented Oct 18, 2020

When i try to use STRING1 or STRING2 or RAW_STRING in translations from the base string, an error is shown.

Steps to replicate: (Translation to ta_IN)
STR_TIMETABLE_TRAVEL_FOR_ESTIMATED
Base lang string: Travel (for {STRING1}, not timetabled)
Translation: பயணம் ({STRING1}, நேர அட்டவணை இடப்படாதது)

Throws the following error:
Error: String command for position 0 is wrong, base language uses {STRING}, the translation uses {STRING1}

I am unable to save string unless these modifiers are corrected to STRING

@glx22
Copy link
Contributor

@glx22 glx22 commented Oct 18, 2020

In translation you just need to replace them with {STRING}, all other kind are for master file only

@TrueBrain
Copy link
Member

@TrueBrain TrueBrain commented Oct 18, 2020

Seems the error needs to be more clear for new people :)

@TrueBrain TrueBrain added enhancement good first issue labels Oct 18, 2020
@Wuzzy2
Copy link

@Wuzzy2 Wuzzy2 commented Jan 19, 2021

Seems the error needs to be more clear for new people :)

I agree, I stumbled over this as well, I had to look it up in the manual to see what was going on. :-(

@Eddi-z
Copy link

@Eddi-z Eddi-z commented Jan 19, 2021

my suggestion would be to just show all {STRINGn} as {STRING} to the translators.

frosch123 added a commit to frosch123/eints that referenced this issue Mar 11, 2021
frosch123 added a commit to frosch123/eints that referenced this issue Mar 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement good first issue
Projects
None yet
Development

No branches or pull requests

5 participants