While looking at a half-translated version of The Events Calendar, I found that some of the messages to be translated were made up of several strings. For instance, to display “Previous Events”, there was a one string containing “Events” and another one containing “Previous %s”. Similarly, for “New Event”, there was a string for “Event” and another one for “New %s”.<\/p>\n
While this may be smart from a programming point of view for reasons I’m definitely not in a position to judge, it’s typically what you shouldn’t<\/strong> do when you want your project to be translated. Fact is that in English, you use the same form of the adjective (e.g. Previous or New) regardless of the noun after it. But in French, to give just one example, the adjective for “new” can have up to 5 forms:<\/p>\n As a result, there is no way we can correctly translate “New %s” for all possible values of %s. Again, this is just one example; some languages are even more complex. The French language does not use case, unlike Russian or Icelandic, for instance.<\/p>\n Anyway, if you want your strings to be translatable:<\/p>\n These are just a few ideas; is there anything else you community translators found difficult\/impossible to translate because of the way it was programmed?<\/p>\n","protected":false},"template":"","class_list":["post-988655","topic","type-topic","status-closed","hentry"],"yoast_head":"\n\n
\n
\nYou may, however, insert a variable part if it’s separated from the rest of the sentence (e.g. after a colon).<\/li>\n