Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
[textpacks] Translating languages strings for Textpattern 4.7
Now that we are close to Textpattern 4.7 beta, it would be great if we could get as many text string translations done as possible – your help is great appreciated. See the Crowdin page for a list of the languages and the current amount each has been completed so far.
Offline
Re: [textpacks] Translating languages strings for Textpattern 4.7
Hi Phil,
I’ll be doing the Greek one but I’ve been flat out for a few months now. I hope that in February I’ll get a breather in which case i’ll be able to give it a few hours.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
#3 2018-01-12 16:46:33
- uli
- Moderator
- From: Cologne
- Registered: 2006-08-15
- Posts: 4,304
Re: [textpacks] Translating languages strings for Textpattern 4.7
General question for all languages:
There is the {name} variable. Is it always a single item that replaces this var, contrary to the self-explanatory {list} var? Or can {name} also be replaced by a list of items?
I’m asking because there are some “plural” examples in English strings using {name}
Links updated: <strong>{name}</strong>.
Plugins updated: <strong>{name}</strong>.
Images uploaded: <strong>{name}</strong>.
etc.
In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links
Offline
Re: [textpacks] Translating languages strings for Textpattern 4.7
Hi Uli, it’s always a single item unless it’s preceded by a colon : – in which case assume it’d be a list. Hope that makes sense.
We changed to this format to accommodate multiple entries and single entries together without having to have two text strings to cover both outcomes.
Offline
Re: [textpacks] Translating languages strings for Textpattern 4.7
We considered going through and amending all tokens to be the same (either {name} or {list}), but it’s quite a bit of upheaval in the code for no major benefit. And we’d have to ensure we found all references and hope plugins also don’t use those strings.
If we do decide to make things more consistent, we’ll do it softly softly over the next few versions.
Last edited by Bloke (2018-01-12 19:51:16)
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
#6 2018-01-14 12:50:58
- uli
- Moderator
- From: Cologne
- Registered: 2006-08-15
- Posts: 4,304
Re: [textpacks] Translating languages strings for Textpattern 4.7
I’m a little confused how to translate the following terms:
- theme (front?)
- skin (back-end?)
- template (used in “Delete all destination templates first?” and two more)
What is what, can somebody please explain a little?
In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links
Offline
#7 2018-01-14 13:24:19
- candyman
- Member
- From: Italy
- Registered: 2006-08-08
- Posts: 684
Re: [textpacks] Translating languages strings for Textpattern 4.7
Completed the Italian translation.
I’ve translated the “theme” with “tema”: other Italians agree?
Offline
Re: [textpacks] Translating languages strings for Textpattern 4.7
Hi Uli,
Theme could be either front or admin-side. Generally the strings refer to the public-side theme.
Skin is just something we used internally to differentiate between front and admin side. Please always refer to it as a ‘theme’ instead of a ‘skin’ in translations.
“Delete all destination templates first?” context is, when you import or export a theme you can select to delete all previous templates or keep ones that aren’t named same as new import/export.
Hope that helps?!
Offline
Re: [textpacks] Translating languages strings for Textpattern 4.7
Hi candyman,
Brilliant stuff, thanks. I’ll move these translations into the 4.7 release. Cheers!
Offline
#10 2018-01-14 13:32:36
- uli
- Moderator
- From: Cologne
- Registered: 2006-08-15
- Posts: 4,304
Re: [textpacks] Translating languages strings for Textpattern 4.7
philwareham wrote #308657:
“Delete all destination templates first?” context is, when you import or export a theme you can select to delete all previous templates or keep ones that aren’t named same as new import/export.
Sorry, I’ve not had an opportunity to try and work with these new TXP features. What element in TXP is a template?
Edit: Could it be easier to understand if you link to Pete’s TXP demo site?
Last edited by uli (2018-01-14 13:36:20)
In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links
Offline
#11 2018-01-14 13:38:56
- candyman
- Member
- From: Italy
- Registered: 2006-08-08
- Posts: 684
Re: [textpacks] Translating languages strings for Textpattern 4.7
Thank you.
Previous translation has been made by other guys: for coherency I’ve followed the same choices (“moduli” for “forms” and so on…). The problem is that some words are understandable and can be left as they are (e.g.: directory, file…): you have to choose if follow an Italian 100% translation or keep a more International one.
I’d like to listen to other Italians about their opinion.
Offline
Re: [textpacks] Translating languages strings for Textpattern 4.7
uli wrote #308659:
Sorry, I’ve not had an opportunity to try and work with these new TXP features. What element in TXP is a template?
Sorry, template means any Pages, Forms and/or Styles file.
Offline