German translation issue

[Richard]

I found a mistake in the German translation.

“event” = “Veranstaltung” instead of “veranstaltung”
“events” = “Veranstaltungen” instead of “veranstaltungen”
“This event has passed.” = “Diese Veranstaltung hat bereits stattgefunden.” instead of “Diese veranstaltung hat bereits stattgefunden.”

The first letter of German nouns is capitalized.

Thank you for correcting the translation,

Richard

[Barry]

Hi Richard,

I’m sorry this has inconvenienced you.

We’re certainly aware of the problem as it stands in relation to German (and possibly other languages) and I’ve raised the priority of the bug report.

We’ll do our best to drop a note in here once we are able to make some headway toward solving this.

Thanks for your patience in the meantime 🙂

[Marcuz]

Same problem here and I have not a few clients that are unhappy about it.

@Barry can you provide a workaround even if it is gone with the next update of The Events Calender.

Thks in advance

Marcuz

[Barry]

Hi Marcuz,

I hesitate to suggest it but it would be possible to create your own custom translations to workaround this. The reason I hesitate is that it can be a pretty complex process, more on that in a second.

The key however is that the word “event” (or “events”) is generally inserted into translations via a placeholder, something like this:

View all %s

In the above example, %s will be replaced with a term meaning “events”. The official German translation for example looks like:

Alle %s anzeigen

However, it would be possible to create a custom translation that dispenses with the placeholder and uses proper capitalization:

Alle Veranstaltungen anzeigen

(Apologies if that actually is not the correct form, but I’m just trying to illustrate how to solve the problem.) With the placeholder removed you have full control over the way the word “event” is translated and capitalized in each string.

Learning how to create translations is a topic in itself and not something we can guide you through here, suffice to say there is plenty of documentation in the WordPress Codex and manuals. You would also need to learn how to deal with strings that contain multiple placeholders if you wish to avoid errors. Example:

This %s will expire in %s

Leaving one and removing the other will cause problems, you’d need to use numbered syntax like this:

This event will expire in %2$s

As you can see, we have replaced the first placeholder and changed the second so it clearly indicates its position – more detail on this can be found in the PHP manual.

Unfortunately it is beyond the scope of support we offer here in the translation forum to go into more detail on this – but do also know that we have increased the priority of the bug report and are actively considering different ways to deal with this.

[Marcuz]

This is more than I expected and in that short amount of time, thank you very much.
Its a bit awkward that the translation with the small “veranstaltung” is not being found in the PO file in the lang folder.
As one client is very persisting, I will have to give it a try, setting up a new PO file, I believe!
Unless, you come up with yet another hint.

Best regards
Marcuz

[Barry]

The thing is that the keywords “event”/”events” are customizable: some people prefer “party”/”parties” or “lecture”/”lectures”, depending on what they use the calendar for. For that reason, we use these %s placeholders.

So those particular keywords are inserted dynamically rather than being drawn from the translation file … but of course different languages have different rules relating to capitalization which leads to problems like this one.

Unless, you come up with yet another hint.

I’m afraid I don’t have much else to suggest right now, besides a quick reminder that you must compile your .po file into a .mo file (otherwise WordPress cannot use it) 🙂

[Sascha]

hi guys,

I have the same issue. Thanks for looking into it.

I do not yet understand why the placeholder %s is replaced with “veranstaltung” without the capitalization. IMO the translation states “Veranstaltung” for “event”.

What to do? 🙂

Please keep us updated.

Cheers Sascha

[Barry]

Hi Sascha, we’ll certainly keep you posted.

I do not yet understand why the placeholder %s is replaced with “veranstaltung” without the capitalization. IMO the translation states “Veranstaltung” for “event”.

The problem is that in some languages and in some sentences it would be bad form to capitalize that word. For that reason there are places where it is converted to all-lowercase. Of course, that doesn’t work well in languages such as German – which we now realize and will address is quickly as we can.

[Sascha]

Thanks Barry! I really appreciate you guys being so responsive. This gives a warm and fuzzy feeling, being a pro license owner. 😉

I hope this will be fixed soon, as I have a naggy customer like Markus as well.

Cheers and thx in advance

Sascha

[Barry]

Definitely, I hope to update you again as soon as possible.

I’d hate to falsely set anyone’s expectations, though: right now our next upcoming release is in the final stages of quality control and so it is pretty unlikely we’ll be able to fit in further code changes (which this fix would require) – so it is likely to take just a little longer to deliver on this issue.

Thanks for your patience in the meantime.

[Konrad]

subscribed (I am also interested in a fix)

[Barry]

Thanks Konrad 🙂

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Geoff]

Hey there!

Just wanted to jump in here and let you know that we released The Events Calendar 4.0.6 last night and it included a fix for this issue. Please check your WordPress updates, or you can also grab the latest copy over at WordPress.org.

Thanks for your patience while we worked on this! Please feel free to open a new thread if you continue to experience the same issue or have any other questions that pop up during updating and we’d be happy to help. 🙂

Cheers!
Geoff

[Author]

Posts