Bad translations with separate words

This topic contains 9 replies, has 3 voices, and was last updated by  Stiofan O’Connor 8 years, 6 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • #27072

    P O
    Expired Member
    Post count: 501

    I see that the translations are not correct. Some words are separate instead of full phrases. That will never work translating to other languages.

    Example:

    This two words:
    – All
    – Places

    Should be one:
    – All Places

    It’s used(1) as “All Places” and that can’t be translated by word, it has to be just one complete phrase. This makes the complete translation words that are separate like this a joke in other languages, it seems that the one developing the site does not know how to speak and write. Not good.

    (1) It’s used in a lot more composed phrases by word, making the plugin imposible to translate. If its translated to match one phrase, all the other ones are incorrect. So its unusable.

    How can this be fixed ?

    Thanks.

    #27093

    Guust
    Moderator
    Post count: 29970

    If you use custom post types, ALL will be used in “all accommodation”, “all schools” etc.
    That is why it is separate.

    When it is used in another composite phrase, you can translate that too, examples:
    Add New Place Category
    Hi there, I would like to enquire about this place. I would like to ask more info about…

    If you use Custom post type, you can change Places there, to use singular etc.

    Can you be a bit more specific where you think it is a problem, then we might be able to suggest a solution.

    #27095

    P O
    Expired Member
    Post count: 501

    No, I have a clean install and the translations are incorrect.

    PO file:
    1- All
    2- Places

    (Forced incorrect) Translation:
    1- Todos
    2- Lugares

    “Todos Lugares” does not exist in Spanish (the same applies for any other language) “Todos los Lugares” is the correct translation and it cant be translated like that, because the strings “All” and “Places” are used in a lot of other places in the site.

    Like this: https://wpgeodirectory.com/support/topic/translate-of-menu/

    So if the theme displays “See All Places”, the translation PO file should have a string for “See All Places”, but it has 3 strings, “See”, “All” and “Places”, terribly wrong.

    Thats what I need to fix.

    Thanks.

    #27097

    Guust
    Moderator
    Post count: 29970

    I guess our translations are not meant for machine translations?
    I’ll ask Stiofan to have a look at your question.

    #27103

    P O
    Expired Member
    Post count: 501

    I guess our translations are not meant for machine translations?

    Actually you have it for machine translations and they are needed for humans that use real phrases, not phrases composed by several words like a machine will do.

    Human: See All Places
    Machine: I need 3 words = See, All and Places (I will make a phrase with this and no one will be able to translate it to another language never, because it will never makes sense and will sound like a machine incorrect translation with very bad grammar)

    Makes sense?

    I’ll ask Stiofan to have a look at your question.

    Thank you.

    #27173

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    Hi,

    If you can point out where any such problems exist exactly then i will be happy to find a solution.

    Thanks,

    Stiofan

    #27182

    P O
    Expired Member
    Post count: 501

    Place.

    That is used to see “place”, “place” categories, “place” tags, add “place”, etc…

    So every single place in the plugin where that word “Place” is used, can’t be translated correctly.

    Example:

    English: Place Categories. (This applies for tags as well)

    In other languages you say in the other way. “Categories for the Place”, using the word categories first.

    So if you translate by separate words, it will never make sense. It will read something like “For The Categories Place”. Which is a mess.

    As Place is used for “Add Place” as well, and you translated it for using it in the categories, it reads “For the Place Add”.

    And so on, all the phrases made by mixing words instead of using real complete phrases, will never work translated, never.

    The strings must be complete and for the correct usage, its imposible to translate something that use random words to create phrases.

    So the PO file should have “Add Place”, “Place Category”, “Place Tags”, in singular and in plural and so on.

    Thanks.

    #27202

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    Thanks for the info, I will have a look at this tomorrow and find a solution, the reason it was done like this in most cases is that the “Place” can be dynamic with the CTP addon, i will look properly tomorrow and try and think of the best solution.

    If you see anything else similar to this just let me know and i’ll look at that too.

    Thanks,

    Stiofan

    #27927

    P O
    Expired Member
    Post count: 501

    Cool, please let me know when its fixed and if a new .po file is available before a full update, please share.

    Thanks.

    #58599

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    We have made some changes in the next version which should solve this for both front and backed translations.

    Thanks,

    Stiofan

Viewing 10 posts - 1 through 10 (of 10 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket