murphy

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Dupped records in the GeoDirectory Core translation #140280

    murphy
    Expired Member
    Post count: 5

    @paolo

    Thanks for the reply.

    Only 1 file per language?

    Each time I have new records translated I just export 2 different files:

    geodirectory-es.mo
    geodirectory-es.po

    Should I upload just one of them?

    Sorry but I really dont know the purposes of each one of the two files.

    Regards

    in reply to: Dupped records in the GeoDirectory Core translation #140248

    murphy
    Expired Member
    Post count: 5

    @paolo

    Thanks for your help because so I can re-translate the Spainish (Spain) language faster, upload new translation and see results for see if there need more fine tune.

    By the way, is there any way to keep control panel in English meantime I concentrate in the frond end translation?

    I ask this because now the problem is that since the language of the backend is imposible to understand I can setup nothing

    Regards!

    in reply to: Translate GeoDirectory and Get 1 Year Free! #138679

    murphy
    Expired Member
    Post count: 5

    Hello all,

    Im trying to setup a Spanish online business directory site and I need to use a good Spanish translation. But just after few days taking a look the “Spanish (Spain)” translation it is more than crazy, in fact I really doubt anybody is running a Spanish GD site using this translation because it looks as Google Translator translation or even worse.

    Even simple words as “Home” that are used in all worldwide home website pages are wrong. By example for the Spanish language it was translated as “House”. Of course If Im at home Im at my house but in a webpage Home is not a House at all.

    “Togo” country was translated as “To go” words, so result is “Ir” verb in Spanish that means “go” verb in English. Of course “Togo” country is not “go” to any place.

    “Turkey” country is translated as a turkeycock animal. Really crazy hehe

    These are just 3 examples of 1 word records translations, If we look at multi-word phrases translations you get annoyed. In fact, I was testing the WP Geo Directory plug-in in English language for few days and all went fine. But after I uploaded es_ES translation to the plug-in and even I put all my neurons to work, I cannot understand anything inside control panel (moreover in the front end I can read / understand nothing uffff).

    So here are my questions:

    1.- Is any way to translate the frontend but keep backend in english to be able to understand anything? So I can continue with the site setup meatime Im fixing the Spanish frontend translation.

    2.- Why many records are dupped? Here are few examples:

    https://www.wpgeodirectory.com/translate/projects/geodirectory/es/default?page=3
    Line 12 (reference language.php:495) and 13 (reference language.php:495) are the same.

    https://www.wpgeodirectory.com/translate/projects/geodirectory/es/default?page=4
    Line 4 (reference language.php:501) and Line 5 (reference language.php:501)

    These are just 2 examples but there are few in every page and even I try update both references/lines I get this error: Error: Identical current or waiting translation already exists.

    Can anybody delete all the duped entries? There are dozens and dozens.

    3.- I can put all my efforts to do a proper and very perfect / serious / correct Spanish (Spain) translation but which warranty we will get that nobody will come after me and kill all hard work done? hehehe It wont be good for the GD community or future Spanish users because there is a really hard work left to be done.

    4.- When you export any “Spanish (Spain)” translation file you get a “geodirectory-es.*” file that you upload and do not work under any WP enviroment until you rename it to “geodirectory-es_ES.*”

    Can anybody make export feature to directly name “Spanish (Spain)” files with “es_ES” suffix by default? So any non-expert user will have working files out of the box.

    5.- Since nobody can understand anything in the Spanish translated frontend and Im ready to concetrate to fix “es_ES” translation properly, how much time will take to have all “waiting” *suggested new translations* to appear as “current”?

    I understand there should have any moderation or filtering but I need some kind of fast “waiting” to “current” applying in order to progress as fast is possible.

    Regards and thanks in advance!

Viewing 3 posts - 1 through 3 (of 3 total)
20% Discount Offer
Hurry! Get your 20% discount before it expires. Get 20% Discount