n1n10
November 9, 2020, 12:50pm
1
Hi good Ghost people,
The new Portal feature looks excellent — very clean and hopefully a great addition to get more members on board and to simplify the sign up process.
However, I do miss the possibility of translating all the English words in the form to my users native language. Which files do I need to edit to accomplish this?
Also, every time I update Ghost, I have to translate signin.js, signup.js and subscribe.js etc. to get the email sign up and log in flow to work in my native tongue. I hope you have this is mind for a future update, which would make Ghost a super solution for many more people around the world, that need to localize their website.
Keep up the good work!
Thanks,
Nic
2 Likes
Congratulations indeed for this new feature, I’m also interested in translation
1 Like
jonock
November 22, 2020, 10:57am
3
The feature turned out really nice. Translations would be even cooler, can we help contribute?
Hi,
Indeed, portal translation capability has been the only one missing feature which has me make consider other platforms por membership.
I would be glad to help too.
Regards
2 Likes
Interested on this topic. Any news about how to proceed with portal translations?
Any news on portal translations??
If the best technical path is set by the authors on how to technically implement it (library to be used, how to integrate portal with an specific language like adding a ?es param or whatever) I would be ready to gif a help on dirty work.
Regards
Apart from the theme translation functionality, a stopping missing feature is the translation of portal and email component. All those messages are hardcoded in js files not translatable by themes.
Any non English spoken ghost webmaster is not able to offer a proper ghost project in his language easily.
I would be glad to help.
Regards
Please vote to give some visibility.
Regads
11 Likes
adoc
January 12, 2021, 9:04am
8
Please make it possible to translate the Portal.
that’s something I really miss
my base of readers, do not speak english, so the email and login pages are a problem to them
can we help ?
LucaG
April 3, 2021, 4:46pm
11
Is there a way to hard code the translation on the server? Similar to how you can do with emails Ghost Email customization - #3 by Izak_Jackson
sigul
April 5, 2021, 8:19am
12
Not sure if this, but you should be able to use the translation helper in the portal files, aren’t you? If it’s limited to hbs maybe a partial?
Hi,
I made this pull request with almost all translations resolved.
TryGhost:main
← muchomasfacil:master
opened 10:46AM - 10 Feb 21 UTC
This is a work in progress for the portal translation.
I have managed to make… almost all the work on translating the portal.
Almost all because I am not an expert and:
- I was not able to treat a pair of cases to propagate the i18n object. But anyway I made the translation and left it commented.
- I do not know how to test all steps but the initial pages (signup, signin) are working in the commit
- I have not taken any time on the build phase
That is as far as I can walk.
References
https://www.i18next.com
https://react.i18next.com
https://www.codeandweb.com/babeledit/tutorials/how-to-translate-your-react-app-with-react-i18next
Here is the list of the touched files and some comments on them:
Portal/src/
data-attributes.js -- PENDING propagate i18n object properly (translations are commented)
actions.js -- PENDING propagate i18n object properly (translations are commented)
App.js -- PENDING propagate i18n object properly (translations are commented)
Portal/src/components
Notification.js -- reference use case -- useTranslation() in const
PopupModal.js -- reference use case -- PopupContent
PopupContentTranslated
Portal/src/components/common
BackButton.js -- reference use case -- with useTranslation in an exported function
CloseButton.js -- reference use case -- with withTranslation in an exported class
PlansSection.js -- PlanOptions() is not ready for translation, it makes decisition based on labels and not based on keys
PopupNotification.js -- is there a better way to translate notificationText() instead of those ugly .1 .2 .3?
Portal/src/components/pages
AccountHomePage.js AccountPlanPage.js -- PENDING propagating i18n in getConfirmationPageTitle() (translations are commented)
AccountProfilePage.js LoadingPage.js MagicLinkPage.js SigninPage.js
SignupPage.js -- reference use case -- withTranslation() -- PENDING of 'Free' string treatment
Portal/src/utils
api.js ?? must be translated???
form.js -- PENDING propagate i18n object properly (translations are commented)
helpers.js -- PENDING propagate i18n object properly (translations
are commented)
It lacks translation of a pair of files (but translations are there commented) where I was not able to instantiate the i18n object (I am not good enough at js) hopping the repository owners would take advantage of it. But sadly, it seems they are not very interesting on portal translation right now.
Hope the pull request could help you.
Regards
Awesome, man… If I had the skills I’ll certainly work on it. Hope it gets merged soon. Congrats for the nice job
No idea how many Swedish users here are, but I am more than happy to help with the Swedish part.
I’ve described another solution for self-hosted Ghost instance on how to override Portal here:
Hello all,
I managed to override Portal (portal.min.js).
I needed it for translation and to remove “Publish with Ghost” button on Portal.
This solution is for self-hosted Ghost instance. I don’t see any possibility to do it in Ghost Pro (I’ve switched to Digital Ocean droplet, so now I can override Portal).
How to override and customize Portal
Check url of your Portal in
/var/www/ghost/versions/{version}/core/shared/config/defaults.json
(can vary on different Ghost versions). In my exampl…
1 Like