Skip to main content

Hello,

We noticed some recent changes in the Dutch translation of various elements in Freshdesk. Unfortunately, some of these new translations are of rather poor quality. Below are some of the changes we noticed, there may be more.

English

Original Dutch version

New Dutch version

Quality

Pending

In behandeling

In afwachting

OK, both “In behandeling” and “In afwachting” are fine.

Tickets I’m watching

Tickets die ik volg

Tickets die ik aan het kijken ben

Poor. “Tickets die ik volg” is better.

Add note

Notitie toevoegen

Aantekening toevoegen

Poor. “Notitie toevoegen” is better

Tickets I raised    

Tickets die ik heb geopend

Tickets die ik heb opgehaald

Poor. “Tickets die ik heb geopend” is better.

 

Could the bad translations be turned back?

The change of “pending” is fine, since “In afwachting” can both be interpretated as “being handled” and “waiting for customer”. I noticed this was an issue for some in other topics.

Kind regards,

Bart De Ridder

The Swedish translation is really bad as well. 

What we see that the system is translated word by word with no context.  

 


Hi Bart & Daniel,

 

Thank you for reaching out to the Freshworks community.

 

We had this checked with our developers team and they have acknowledged the change as a bug. Our developers are working on reverting the same. I shall keep you posted with regard to further updates on this.

 

Thank you.


This happened today with our freshservice as well.

In behandeling is now suddenly translated as In afwachting. 


This happened today with our freshservice as well.

In behandeling is now suddenly translated as In afwachting. 

 

Thanks for bringing this to our attention, @Benjamin Vanderroost 

Adding @rajagopal.baladhandayutham to share his insights on the reported issue with dutch translations in Freshservice. 

 

Cheers,

 

 


@Benjamin Vanderroost We are having this investigated with our engineering team and we’ll keep you posted on our findings soon.


@Benjamin Vanderroost Our team has acknowledged this to be a bug, we’ll keep you posted with further updates when this is being fixed.


Reply