This topic has 6 replies, 3 voices, and was last updated 8 years, 4 months ago ago by Stan Russell
In the Spanish transaltion of the phrase “go to previous page” in the header breadcrumbs now is “Volver a pagina anterior” and has to be “Volver a página anterior”.
We know that we can change in the .po file, but each time we upgarde the theme we will have to change this again. Example: http://lospilareseditorial.com/madrid/gastronomia-y-sabores-de-madrid/
And in Spanish is página instead pagina. It´s just an accent mark
So if you change this in your theme files in the next releases will be fine
Thanks in advance
Rodrigo
We have two website with your theme
http://lospilareseditorial.com/
http://silu.es/
Hello,
You may try to set special character using html code http://www.ascii.cl/htmlcodes.htm
http://storage5.static.itmages.com/i/15/1229/h_1451387291_8244586_272f502d3c.png
Best regards,
Jack Richardson.
Hi Jackson,
thanks for yopur answer,. I know that I can change manually >(.po file), but if in your defeault Spanish language you include “Volver a página anterior” instead “Volver a pagina anterior” will be with the right orthography.
Is not an urgent issue
Rodrigo
Hello,
We don’t have Spanish translation files in the theme and we don’t edit current translation files during the theme update.
Only you edit your files.
Have you tried the solution with html code?
Best regards,
Jack Richardson.
Hello Jack,
sorry for this issue. In the first ROYAL web site one member of my team had developed the Spanish translation , and the member started the new ROYAL site and when I reviewed the NEW site I detected the wrong word, and I thought that was in the theme core.
Anyway we solved it with editing .po file with the right word.
Thanks for your support, and sorry again for this mistake 😉
You can mark this ticket as “solved”
Hello Mentadata,
we are happy that your problem is solved! Have a nice day!
Regards,
Stan Russell.
The issue related to '‘Translation BREADCRUMBS "go to previous page" in Spanis to "Volver a pagina ante’' has been successfully resolved, and the topic is now closed for further responses