I would like to be part of this effort to make all of the official themes multilingual. Is there already an ongoing work in a branch, or a group that I can involve?
Hey folks! Iām not Hannah (clearly!), but Iāll tell you what she said when I asked about translating official themes. (That was ~September, 2024.)
The current code that handles theme translation is old and creaky, something that the ghost team wrote because there wasnāt anything great out there when they needed, and itās just not super great. Theyād like to switch theme translation over to the i18next package, which is the (supported, not home-grown) package that handles all the rest of Ghost translation. Thatās the current blocker. They donāt want to handle translations of official themes until theyāve switched over the i18next and are sure that the current string formatting is whatās actually going to be supported.
I have maybe half of that work done and in a draft PR sitting in Github. I hope to get back to it at some point, but Iām struggling to keep up with my paying work, and I canāt donate that time right now. If someone is ready to go on it, feel free to fork my fork and make some progress. Itās here: [WIP] Theme i18n by cathysarisky Ā· Pull Request #21490 Ā· TryGhost/Ghost Ā· GitHub
(If someone would like to fund that work for a couple months from now, please get in touch.)
Edit: Golly, I should really read the whole thread before responding to the last bit of it, where you can scroll up and read what Hannah said herself. (Although I think I added a little extra context from a separate convo I had with her, at least!)
2 Likes
Iāll take a look at this and try to figure out why itās so challenging. But since you already looked at it, it would be great if you can roughly point out the challenging part(s) of this work.
1 Like
Fine, but both initiatives, are incomplete and will not work, because as show in docs, theme translation MUST have āpagination.hbsā and ānavigation.hbsā at partials folder and the translation tags there. I did this, and now my Casper Fork works.
As for now, Ghost are not accepting i18 translations in default themes, since they are working in i18 for Ghost, and i18 are not stable yet. From main Ghost dev perspective is ok. Since, need to deal with some dilemmas, like the logical values that are in āpackage.jsonā and are used in theme templates *.hbs, etc.
But, for many people on community, they want to use Ghost in production with i18 for their audience. In this way, I create a Github Organization where I will add all OpenSource Ghost Themes and adjust i18 needs. Everyone want to help. Are welcoming.
Hey folks!
Itās Sunday, so Iām goofing off (instead of working) by ripping out the existing theme translation package and making it use i18next.
Iāve been making use of the Source-i18n package for testing (thanks @NinoBagatello , and I see thereās a Casper fork (from @jobdiogenes ) that I can also try.
However, I know Iāve seen more complex usage in some paid themes, and Iād like to make sure my re-implementation isnāt going to break those.
Soā¦ I could use some help. Is there anyone making āinterestingā use of the ātā function in themes, including passing in variables, nested t, etc, able to help me manually test the edge cases?
You could either: 1) Send me a link to download your theme, preferably with demo content & any required routing files or 2) grab my version of Ghost and install somewhere and test it yourself. (āØTheme i18n converted to use i18next (with feature flag) by cathysarisky Ā· Pull Request #23161 Ā· TryGhost/Ghost Ā· GitHub )
Note: If you provide me with access to a paid or non-MIT licensed theme, Iāll only use it for testing, never for installing anywhere beyond my local dev setup. :) Thanks in advance!
Update: I see thereās a bunch of themes in jobdiogenes 's Github org. Iāll go explore there. 
2 Likes
Hi @NinoBagatello, will there be an update soon to take into account the new social links?
@bastien the latest release of source is 1.4.1 from december 2024. Releases Ā· TryGhost/Source Ā· GitHub
as soon as there is a new release i will update.
1 Like
@NinoBagatello , Source has definitely been updated more recently than December, to add the new staff member socials. :)
1 Like
@Cathy_Sarisky I see there is a Git tag 1.5.0 that wasnt marked as github release. so i got no notification about it.
Source-i18n updated to v1.5.0 Git tag of upstream:
2 Likes
Thank you @NinoBagatello
@Cathy_Sarisky @NinoBagatello It may be a native flaw in the Source theme, but I donāt understand why there isnāt a dedicated icon for the personal website. There are icons for all the social networks but you have to click on the name to access the authorās website, which isnāt intuitive and is almost invisible on mobile.
What should be done to correct this problem?
If itās in native source, filing an issue report either in the bugs forum or over in the github repo would be a reasonable action.
Alternately, nothing prevents you from editing your copy of the theme to have the behavior you want. :)
1 Like
Hey translator friends! I can use some help over here:
1 Like
@Cathy_Sarisky thank you. I donāt code unfortunately so I am not sure I could do this correctly and I think this improvement should benefit to anyone using the theme. I just requested it here : An author's profile page needs design improvements Ā· Issue #84 Ā· TryGhost/Source Ā· GitHub
Is it okay to do it this way ?