sv.json file for Domain.Shared/Localization/AppName
{
"Culture": "sv",
"Texts": {
"AppName": "MY_APP_NAME",
"Menu:ContactUs": "Kontakta oss",
"Menu:ArticleSample": "Artikelexempel",
"Home": "Hem",
"Date": "Datum",
"Permission:Dashboard": "Dashboard",
"Menu:Dashboard": "Dashboard",
"Menu:HomePage": "Hemsida",
"Dashboard": "Dashboard",
"ExternalProvider:Google": "Google",
"ExternalProvider:Google:ClientId": "Klient-ID",
"ExternalProvider:Google:ClientSecret": "Klienthemlighet",
"ExternalProvider:Microsoft": "Microsoft",
"ExternalProvider:Microsoft:ClientId": "Klient-ID",
"ExternalProvider:Microsoft:ClientSecret": "Klienthemlighet",
"ExternalProvider:Twitter": "Twitter (X)",
"ExternalProvider:Twitter:ConsumerKey": "Konsumentnyckel",
"ExternalProvider:Twitter:ConsumerSecret": "Konsumenthemlighet",
"NewsletterHeader": "Prenumerera på nyhetsbrevet!",
"NewsletterInfo": "Få information om de senaste händelserna.",
"NewsletterPreference_Default": "Standardnyhetsbrev",
"NewsletterPrivacyAcceptMessage": "Jag accepterar <a href='/privacy-policy'>Sekretesspolicy</a>.",
"Language": "Språk",
"Search": "Söka",
"LoadMore": "Ladda mer",
"Settings": "Inställningar",
"Theme": "Tema",
"DeviceTheme": "Enhetstema",
"Dark": "Mörk",
"Light": "Ljus",
"Unspecified": "System",
"SeeAllUsers": "Se Alla användare",
"TakePhoto": "Ta foto",
"ChoosePhoto": "Välj Foto",
"Menu:Home": "Hem",
"LongWelcomeMessage": "Välkommen till ansökan. ",
"Welcome": "Välkomna"
}
}
Thanks!
I noticed the term "Dashboard" seem to be missing in the JSON (even in English), not an obvious translation for that in Swedish though (besides a direct translation that sounds really funny) so probably better to keep as it is.
If not already modified, there needs to be added Swedish to AbpLocalizationOptions also
options.Languages.Add(new LanguageInfo("sv", "sv", "Svenska"));
There is also the sv.json file for Domain.Shared/Localization which I will provide in a follow up message. Not sure how that works 100% since there is supposed to be the chosen appname for where we have put "MY_APP_NAME", that is probably automatic I would guess.
This entry seems incorrect in English also BTW, should probably be "provided a" rather than "provide" and the translation "Du har redan svarat" but there are probably quite a few of these if you start to nitpick, guess the most important is that the main UI is as correct as possible.
{
"LocalizationKey": "Forms:0001",
"Reference": "You already provide response.",
"Target": "Du ger redan svar."
},
Thank you for providing more details on this. However, I am unable to produce the same problem with a project created by using this command
abp new MyTestApp -t app -u angular -csf. May I know whether you have made a related change or come across another problem and produced such problem?
Has passed quite some time since this topic was created, we will try to test this again with latest ABP version when we get a chance to. Not sure if things might have changed since then. Please lets keep this ticket open until then.
hi
You can share the
abp-translation.jsonwhen you add new translated texts.Thanks.
The bot will close the question regularly. You can reopen it at any time.
Hi,
Have sent you the translated file now with some additional questions.
With this being a commercial product and there are now things like DeepL available at a low cost, I think that ABP should take over the responsibility of providing translations for the mostly used/requested languages. This especially as the translation process is quite complicated due to not all source code being public (or available to all ABP Commercial customers) and the process itself has lots of potential pitfalls. Also, as I understand it, there is no way for us to test a translated JSON ourselves as that would most likely require access to all the source code to be able to "apply" it. Depending on which of the instructions you read on how to translate, there already seem to be built in support for DeepL in the ABP translation process, so it should be quite easy for ABP Team to do the translation even though you probably do not speak the language yourselves.
We used DeepL ourselves to do the translation, and then just checked the result afterwards as much as we could and made some small changes. While not perfect, I think it is probably good enough.
Thanks.
This issue is still not completed (although currently on hold on our side).
No yet.this work is still in progress
So no support for React Native/ Expo in ABP for now since the current implementation is based on the now deprecated Expo SDK 49?
ABP prices going up, ABP services going down...
：）
The template is very raw. major functionalities like login, redux and localization is still pending it seems that made me worry about the timeline.
So what is actually included then besides what comes with a standard Expo project?
Hello again. If you mean that the navbar cannot be pinned for the 1200px, the expected behavior is not satisfied. Normally, it should be pinned if the size is 1200px and wider, and open on hover if the width is less. But, it seems working in both cases.
I have also checked on different browsers such as Safari, Opera and Firefox. If you are getting this error for another browser type, I can assist further.
It covers parts of the page content at 1200 px. Been a while since I created this but as I recall we only tested it in Chrome (on Windows 11) as that is the most popular browser.
Hi,
I understand that, In fact, you don't have to worry about it, the main difference between the old and the new template is the configuration file. If you want, you can absolutely use the new template to develop your application. The beta phase I mentioned is the studio, not the template.
Thanks.
What is the target date for when Docker support will be added to the new templates? The link given above https://github.com/abpframework/abp/milestone/107 does not seem to include a task for Docker from what I can see?
