reopen: post type name translation not possible

your way to translate individual post type names, mentioned in the topic linked above, doesn’t help us at all. We don’t use custom post types, we use places and events only.
So, I tried using GD Tools as described, but the file db-language.php is empty, there is no string added.

again, the problematic is about the following:
“%s Title” and “%s Description”

In German the correct translation for “%s Title” would be:
“Place Title” = “Titel des Platzes”
“Event Title” = “Titel der Veranstaltung”

Do you see the difference?
The genitive declination of “place” is in German with the pronoun “des” (and this is different from “der” – can you read?), and ends on “es”, the German word for event is “Veranstaltung” und doesn’t have a genitive ending.

Is that so hard to understand?

So, since I had to repeat this, I repeat my suggestion for a patch, too:

As the two main posttypes are places and events, I’d suggest to add a conditional clause:
in geodirectory_template_actions.php this is line 2215:

<label><?php echo sprintf( __('%s Title', 'geodirectory'), $cpt_singular_name ); ?><span>*</span> </label>

change it to:

<label><?php 
if($cpt_singular_name == 'gd_place')
_e('Place Title', 'geodirectory');
elseif($cpt_singular_name == 'gd_event')
_e('Event Title', 'geodirectory');
else
echo sprintf( __('%s Title', 'geodirectory'), $cpt_singular_name ); 
?><span>*</span> </label>

the same for description would be in line 2267:

<label><?php echo sprintf( __('%s Description', 'geodirectory'), $cpt_singular_name ); ?><span><?php if ($desc_limit != '0') { echo '*'; } ?></span> </label>

change it to:

<label><?php 
if($cpt_singular_name == 'gd_place')
_e('Place Description', 'geodirectory');
elseif($cpt_singular_name == 'gd_event')
_e('Event Description', 'geodirectory');
else
echo sprintf( __('%s Description', 'geodirectory'), $cpt_singular_name ); 
?><span><?php if ($desc_limit != '0') { echo '*'; } ?></span> </label>

Hi Stiofan,

thanks for your reply! Sorry for maybe wrong accusing. (We got that feeling afer the security issues, but that’s another topic.)

Yes, my solution would only work for places and events, that’s right. For other CPTs it would stay as it is.
I think your idea would not add this to the po files. I’m not sure about your mentioned functionality. But when I tried it before, the db-language.php stayed empty, no strings added to po or anywhere.

I now installed your custom post types addon to get an idea of it. I didn’t start using it yet, but if it works as expected it could be an idea to add the mentioned strings to the LABELS in advanced mode. (“Place Title” and “Place Description” to the label section of advanced edit mode of post type gd_place, and “Event Title” and “Event Description” to the label section of advanced edit mode of post type gd_event).
What do you think about that?

After backing up my testing environment and setting up the custom post types to our use, I’ll let you know.

yes filters would be fine