WPLM Translation Don´t Update on The Frontend
This topic contains 34 replies, has 4 voices, and was last updated by mambo 8 years, 10 months ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support TicketTagged: translation, WPLM
-
AuthorPosts
-
August 3, 2015 at 2:21 pm #47924
Hi.
As far as I can, bellow you´ll find the strings I´m still having problem with:
1 – geodirectory-pt_PT
– Tags are short keywords, with no space within.(eg: tag1, tag2, tag3) Up to 4 characters only for this package.
– Please accept terms and conditions2 – geodirlocation-pt_PT
– Change Location/Alterar Local
– City/Cidade
– Region/Província
– Neighbourhood/Bairro
– Select Neighbourhood/Selecionar Bairro3 – geodir_payments-pt_PT
– Select Package
– Free: number of publish days are unlimited (0.00
– number of publish days are / %s : o número de dias de publicação são %s (<span id=”%s”>%s %s</span>) “Widgets”
– Código do Cupão/Código do Cupão
– Enter Coupon Code/Digite o Código de Cupão
– Enter coupon code here (optional)/Digite o código de cupão aqui (opcional)4 – geodirevents-pt_PT
– Event (widget title)5 – Avad Theme
– Read More/ Ler Mais6 – Correct “…Locaisem ” to “…Locais em” from “All Places”
Thanks.
August 6, 2015 at 3:11 pm #48404Hey guys, please don´t forget about me…
Regards!
August 6, 2015 at 9:05 pm #48457Hi and sorry for the delay,
1 as Stiofan said having the prices and payments add-on installed, this label for tags is taken over by the payments po file. I did a quick test on your website and it works.
2 I just resaved your po file and uploaded the mo file generated and it works.
3 The price text is custom text entered by you. We can make it translatable like custom fields, but I’m not positive it’s already feasible. I’ll ask developers. The rest is working
4 Widget titles are translated via WPML because they are user generated strings, not po file
5 Ask Avada support for this
6 Not sure this can be done. I need to ask to Stiofan.
Thanks
August 7, 2015 at 10:01 am #48485I don’t really understand what you need to do with #6 can you explain it more for me please?
Thanks,
Stiofan
August 8, 2015 at 11:02 am #48656Hi.
I don´t understand. The list I´ve sent are from strings I translated but don´t reflect on the frontend when I change from PT to EN, even after confirm that they are in fact translated in the .mo files.
I don´t know if I´m missing something, but from what I can see, the problem still there.
# 6 – The word “…Locaisem ” isn´t well. It should separate the last two letters to stay “…Locais em”.
Thanks.
August 8, 2015 at 11:05 am #48657OK i’m even more confused about #6 now, we provide “All Places” and you translate it to what you want but you are telling us YOUR translation is wrong? Is this your translation or what? 🙁
Please explain it again.
Stiofan
August 8, 2015 at 11:58 am #48672Please, let me explain…
In english, the word is correct “All Places in…” which in PT should be “Todos Locais em…”, but by my mystake I joined the two last letters when I translated to PT and now I have “Todos Locaisem…”. I can´t find this sentence so I can separate the last two letters.
I´m not saying that the problem was about your translation. I simple can´t find that word to separate those two.
Got it?
August 8, 2015 at 12:11 pm #48674OK, thanks for explaining and it helped me locate the problem. When you translated the workd ” in ” you removed the spaces in the translation “em” please check/fix/uplaod and that should work 🙂
Stiofan
August 8, 2015 at 12:21 pm #48677Ok. but where do I find it? Which .po file? Is the geodirlocation-pt_PT.po file?
That´s my problem.
August 8, 2015 at 2:07 pm #48686Hi Mambo,
that is the geodirectory po file.
Did you know that you can search for strings with poedit?
Just open a file, click CTRL+F and search All Places in.
Let us know,
Thanks
August 10, 2015 at 11:47 am #48822Hello Paolo.
I couldn´t understand about the other strings with the problem of not reflecting on the frontend. By your explanation, major is solved but I still facing the same problem.
# 1 – In fact about the tag info it was “taken over by the payment .po file” as Paolo said and I was able to change it. But “Please accept terms and conditions” is translated in the geodirectory-pt_PT .po file but still don´t update.
# 2 – When you change the language to EN those words remain in PT when should reflect the translation are made on the geodirlocation_pt_PT.po file.
– Change Location/Alterar Local
– City/Cidade
– Region/Província
– Neighbourhood/Bairro
– Select Neighbourhood/Selecionar Bairro# 3 – The same as #2. Please try to change to EN and you´ll see that those translated words don´t change to EN
– Código do Cupão(PT)/Código do Cupão(EN)
– Enter Coupon Code(PT)/Digite o Código de Cupão(EN)
– Enter coupon code here (optional)(PT)/Digite o código de cupão aqui (opcional)(EN)Except those which are already in EN:
– Free: number of publish days are unlimited (0.00
– number of publish days are / %s : o número de dias de publicação são %s (<span id=”%s”>%s %s</span>) “Widgets”# 4 – The Event word appears under the Google Maps on the home page, after Places|”Event” (EN). In PT stay Locais|”Eventos”.
# 6 – Let me tell you that this was the FIRST thing I did, but just in case of do it with a wrong file I did it again in each .po file but with no result.
Regards.
August 11, 2015 at 5:16 pm #49018This reply has been marked as private.August 12, 2015 at 9:49 am #49082This reply has been marked as private.August 18, 2015 at 4:55 pm #49894Hello Tiofan.
Is just to say that the translation issue you solved yesterday. Just to update this ticket.
Regards.
August 18, 2015 at 4:57 pm #49895Thanks 🙂
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket