Shouldn't the title of the admin-pages be changed too if you want to change 'WordPress' into 'YourDomain' or something?
I can get the 'Howdy' to change into something else, but if I set a text change for 'WordPress' into 'YourDomain' the wp-admin title (as in the title-tags) doesn't get changed.
Shouldn't the title of the admin-pages be changed too if you want to change 'WordPress' into 'YourDomain' or something?
I can get the 'Howdy' to change into something else, but if I set a text change for 'WordPress' into 'YourDomain' the wp-admin title (as in the title-tags) doesn't get changed.
With belt and braces uncommented, it will change all translatable text and everything above the content body and in the footer, including the header.
Something to note: the belt and braces functionality isn't run on the Text change admin page, as this would cause "unpredictabilities". You need to navigate to a different page to check that it is making the change in the title.
It also changes nothing on the front end of the site as it is an admin area plugin only.
Don't think that changing it on the frontend would be a good idea. For instance, if you change WordPress into the name of your website and people are bloggin about WordPress that would also change into the name of your website (which would confuse everyone).
I guess the reason why the title-tag isn't changing is because it's put in there directly (wp-admin/admin-header.php). Oh well, changing that one thing manually isn't that hard :)
Belt and braces is in specifically to change that, as in it's not translatable. It's currently running on edublogs.org and changing the title tag, can you make sure that the line Andrew highlighted (at the top of the php file is un-commented).
Enter the translation options in the Text change page (click on the case insensitive option), and save the changes.
Then navigate to the Dashboard (or some other page) and check the change.
If that doesn't work can you list your text change settings, as their order may be conflicting with each other.
Well, apparently the checkbox did it (case-insensitive). Only thing is this: " 2. This WILL change a users blog content, comments, tags, categories, links, etc... when viewed in the admin area."
I don't want that to happen, so I'll change that one manually.
It's if you want to limit the change to certain plugins.
So, for example, if in a plugins code it has something like:
__('user','mypluginname')
Then entering mypluginname in the text domain ensures that only that bit of text, within that plugin is changed and any other text throughout the system is left alone.
Regarding your earlier message.
2. This WILL change a users blog content, comments, tags, categories, links, etc... when viewed in the admin area.
This version doesn't change the user content now as it stops processing before the user content and starts again afterwards. So that message really needs to be taken out. Sorry for worrying you. :(
So again: Does this only change text taken from the database? I would like to use this to translate common terms in themes so that I can use any wordpress theme without having to go into them to edit them. I.e replace words like "Categories".
What's would be the best solution to translate the site frontend text that haven't been translated by placing. po and .mo files in the language folder aside just editing the code on the file. But which file is it actualy that I should edit ? I thought html.css but couldn't find it ? I'm using scholar theme.
There always remain text in english especially when I add plugins so I would like to know if there is a solution to translate all the administration texts of the plugins. It will be my job to manage the site for a while but it will not be so eternally and if people can't get to see everything in their language when they take it on this might be a problem.
7430 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Erstwhile founder
—
9th March 2010 (2 years ago)
#
Hiya,
What's would be the best solution to translate the site frontend text that haven't been translated by placing. po and .mo files in the language folder
It really depends on which bit of text you're referring to. Most text should be translatable via language files but sometimes you'll come across text that has not been prepared for translation. In those cases you'll need to edit the file to translate the text.
I thought html.css but couldn't find it ? I'm using scholar theme.
It's best to start a new thread pointing out which bit of text you can't translate.
Btw, in the future please start a new thread if you're question/issue isn't identical to the one being discussed in an existing thread.
Responses (25)
Erstwhile founder — 24th August 2009 (2 years ago) #
We'll check to see if this is a bug. The plugin changes what it can but I'm afraid it just can't change everything.
Thanks,
Andrew
Erstwhile founder — 24th August 2009 (2 years ago) #
Hiya,
Can you try uncommenting the following line:
//define('SWTC-BELTANDBRACES', 'yes');
Thanks,
Andrew
Member — 25th August 2009 (2 years ago) #
Doesn't change anything in the title-tag.
Member — 25th August 2009 (2 years ago) #
Seems like this only changes post content? I don't know, but it doesn't change text that are in themes.
Trying to translate with this ;). It would be perfect to just translate the common words like "Categories" etc and be able to use any theme.
Developer — 25th August 2009 (2 years ago) #
With belt and braces uncommented, it will change all translatable text and everything above the content body and in the footer, including the header.
Something to note: the belt and braces functionality isn't run on the Text change admin page, as this would cause "unpredictabilities". You need to navigate to a different page to check that it is making the change in the title.
It also changes nothing on the front end of the site as it is an admin area plugin only.
rgds
Barry
Member — 25th August 2009 (2 years ago) #
Don't think that changing it on the frontend would be a good idea. For instance, if you change WordPress into the name of your website and people are bloggin about WordPress that would also change into the name of your website (which would confuse everyone).
Member — 25th August 2009 (2 years ago) #
I guess the reason why the title-tag isn't changing is because it's put in there directly (wp-admin/admin-header.php). Oh well, changing that one thing manually isn't that hard :)
Developer — 25th August 2009 (2 years ago) #
Belt and braces is in specifically to change that, as in it's not translatable. It's currently running on edublogs.org and changing the title tag, can you make sure that the line Andrew highlighted (at the top of the php file is un-commented).
Enter the translation options in the Text change page (click on the case insensitive option), and save the changes.
Then navigate to the Dashboard (or some other page) and check the change.
If that doesn't work can you list your text change settings, as their order may be conflicting with each other.
Member — 25th August 2009 (2 years ago) #
Well, apparently the checkbox did it (case-insensitive). Only thing is this: " 2. This WILL change a users blog content, comments, tags, categories, links, etc... when viewed in the admin area."
I don't want that to happen, so I'll change that one manually.
Developer — 25th August 2009 (2 years ago) #
Hi again Hiranthi
This is the setting I have on my system (link to image as I can't seem to get it to embed):
Text change Screenshot
I've added some extra tags on the end to ensure that it only changes the WordPress in the title.
Developer — 25th August 2009 (2 years ago) #
Or alternatively (if the link above doesn't work):
Find text: WordPress\<\/title\>
Replace text: StayPress
The additional slashes are because the system uses regular expressions to hand the change.
Member — 25th August 2009 (2 years ago) #
Oooh, that's nice :) Just added that and it works like a charm, thanks! :)
btw, d'you know what that 'in this text domain' is for?
Developer — 25th August 2009 (2 years ago) #
It's if you want to limit the change to certain plugins.
So, for example, if in a plugins code it has something like:
__('user','mypluginname')
Then entering mypluginname in the text domain ensures that only that bit of text, within that plugin is changed and any other text throughout the system is left alone.
Member — 25th August 2009 (2 years ago) #
Ooh right :) I knew I heard about 'text domain' before, just couldn't remember where/what context etc.. ;)
Developer — 25th August 2009 (2 years ago) #
Regarding your earlier message.
2. This WILL change a users blog content, comments, tags, categories, links, etc... when viewed in the admin area.
This version doesn't change the user content now as it stops processing before the user content and starts again afterwards. So that message really needs to be taken out. Sorry for worrying you. :(
Rgds
Barry
Member — 25th August 2009 (2 years ago) #
Oh, that's ok. The solution you offered in your partial screenshot made me stop worrying ;)
But that's good news :)
Developer — 25th August 2009 (2 years ago) #
Sorry just realised I made a booboo.
The replacement text (in my example) should be:
StayPress</title>
With the title close tag on the end, otherwise it will leave that off. You don't need the extra slashes for the replacement text.
Member — 25th August 2009 (2 years ago) #
So again: Does this only change text taken from the database? I would like to use this to translate common terms in themes so that I can use any wordpress theme without having to go into them to edit them. I.e replace words like "Categories".
Developer — 25th August 2009 (2 years ago) #
It doesn't work on the front-end of the site. So only text in the admin areas is changeable.
Member — 26th August 2009 (2 years ago) #
Aha. Thanks.
Member — 23rd February 2010 (2 years ago) #
I suppse this plugin can not be used to say,, replace "Just another weblog" with NOTHING on all created blogs?? I tried,, but no luck
Erstwhile founder — 23rd February 2010 (2 years ago) #
Correct. This plugin is meant to allow you to change any hardcoded text in the admin panel across all blogs.
Thanks,
Andrew
Member — 23rd February 2010 (2 years ago) #
I see. Thanks
Member — 9th March 2010 (2 years ago) #
Hi !
What's would be the best solution to translate the site frontend text that haven't been translated by placing. po and .mo files in the language folder aside just editing the code on the file. But which file is it actualy that I should edit ? I thought html.css but couldn't find it ? I'm using scholar theme.
There always remain text in english especially when I add plugins so I would like to know if there is a solution to translate all the administration texts of the plugins. It will be my job to manage the site for a while but it will not be so eternally and if people can't get to see everything in their language when they take it on this might be a problem.
Any advice welcomed !
There is a super nice conversation about the edupunk mouvement on youtube if that interests anyone.
http://www.youtube.com/results?search_query=edupunk&search_type=&aq=f
Erstwhile founder — 9th March 2010 (2 years ago) #
Hiya,
It really depends on which bit of text you're referring to. Most text should be translatable via language files but sometimes you'll come across text that has not been prepared for translation. In those cases you'll need to edit the file to translate the text.
It's best to start a new thread pointing out which bit of text you can't translate.
Btw, in the future please start a new thread if you're question/issue isn't identical to the one being discussed in an existing thread.
Thanks,
Andrew
Become a member