Topic-icon Notification mail and messages in Swedish

Active Subscriptions:

None
10 years 7 months ago #37221 by joomleb
Hi Alex, so:
COM_JFBCONNECT_THANKS_FOR_SIGNING_IN and the other two key values (shown into the imagines) exist in the file /language/en_GB/en_GB.com_jfbconnect.ini without the semi-colon. They exist also in the file /language/it_IT/it_IT.com_jfbconnect.ini I'm using but with the semi-colon.

So,
1 - if "JFBConnect should fall back to the English *translated* string, not the key value" with the semi-colon, something is not going in the right way in JFBConnect.
2 - if "JFBConnect should fall back to the English *translated* string, not the key value" without the semi-colon, something is not going in the right way in the languages file.
Well, I'm not a programmer and I don't know how transiflex work, but in the simpe logic: English is the "standard" language file. English is the language file always 100% translated. Why don't simply copy and rename the English file into all the other languages and start from those ones ?
If I haven't yet translated a word the English one is shown.

Waiting for your instructions,
Please,Where can I find any Transifex guide here to learn how you want translation files are managed ?
Thanks
The topic has been locked.
Support Specialist
10 years 7 months ago #37246 by alzander
Try going into the /it_IT file and simply removing the ; (and any spaces) from the beginning of the sentence you want to work with. Then, see if that fixes the issue. You may want to change the value on the right hand side of the string as well to be what you want to show. We'll look into why the en_GB strings aren't being defaulted to properly.

As for Transifex, let's not worry about that for now. It will just confuse the issue and right now, I just want your strings to properly show up.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 7 months ago - 10 years 7 months ago #37251 by joomleb
Hi Alex,
I confirm you that going into the /it_IT file, removing the ; (and any spaces) from the beginning of the sentence fixes the issue.

Waiting your confirm and your instructions on how you want translations are made (to don't repeat same work more times and do something useful for all),
Thanks

PS
I noted right now that from yesterday JFBConnect 5.1.2 is been released. Be careful, all what I test is on previous 5.1.1 release.
O changelog I can read: "Enh: Language updates".
Don't knowing what it mean exactly, please, let me know if I have to update and re-test...
Last edit: 10 years 7 months ago by joomleb.
The topic has been locked.
Support Specialist
10 years 7 months ago #37327 by alzander
Glad to hear that worked. For language string updates, you can feel free to just email those to me if you don't want to deal with Transifex at This email address is being protected from spambots. You need JavaScript enabled to view it.

If you want to use Transifex to keep things up to date, you should:
* Go to www.transifex.com/projects/p/jfbconnect/language/it_IT/
* Join / Login to Transifex if you haven't already
* Apply to be a part of the Italian translation project

Before each release, we pull in any updates from Transifex so that all users can benefit.

Finally, the v5.1.2 language updates are some minor fixes for new strings or missing strings in the 5.1.1 release. There was no major change to how language strings are loaded.

I hope that helps,
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 7 months ago #37340 by joomleb
Last but not least important:

alzander wrote: JFBConnect should fall back to the English *translated* string, not the key value.


This has been solved in the 5.1.2 reease ?
The topic has been locked.
Support Specialist
10 years 7 months ago #37347 by alzander
No, that hasn't been solved. It's something we're looking into and should be happening, but we'll be investigating it for the next release.

I hope that helps,
Alex
The topic has been locked.
Active Subscriptions:

None
10 years 7 months ago #37358 by joomleb
Thanks,
Please, let us know as it's been solved :D
The topic has been locked.