[actiondreamer]

Thank you Sakin for your help. Finally, my host provider discovered some weird redirection in the .htaccess (¡?) (I don’t understand very well but the problem is gone). Have a nice day.

[actiondreamer]

Hi Sakin, of course you can’t see the PDF file, that’s the problem. The file was uploaded as usual… I have been testing with JPEG’s, no problem with them, only with PDF’s
When you click the PDF link, see the address in the browser, it is exactly the URL file

[actiondreamer]

I have the same problem
No update links in my account

[actiondreamer]

It works!

Thank you

[actiondreamer]

Normal
0

21

false
false
false

ES
X-NONE
X-NONE

MicrosoftInternetExplorer4

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:”Tabla normal”;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:””;
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:”Calibri”,”sans-serif”;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:”Times New Roman”;
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}

In the recent Catchbox Pro theme upgrade you delivered me a .pot file under the language folder.

What I need to do is to convert the .pot to.po to .mo by any means. Let’s say Poedit or the plugin Codestyling Localization.

This procedure leads me to work again in translation.

1) Please give a recommendation for doing the best localization procedure.

==

2) What can you tell about the following?

When I tried to do the localization to Spanish using the Codestyling plugin. It shows these messages:

(I understand that these messages are related with localization standard coding practices, rather than the specific plugin procedures)

ERROR: The actual loaded translation content does not match the textdomain: catchbox
Expect, that any text you translate will not occure as long as the textdomain is mismatching!
This is a coding issue at the source files you try to translate, please contact the original Author and explain this mismatch.

WARNING: The actual loaded translation content contains mixed textdomains and is not pure translateable within one textdomain.
It seems, that there is code contained extracted out of other plugins, themes or widgets and used by copy & paste inside some source files.
The affected unknown textdomains are: simplecatch, catchthemes

What is a textdomain?

Textdomains are used to specified the context for the translation file to be loaded and processed. If a component tries to load a translation file using a textdomain, all texts assigned to this domain gets translated during page creation.

The extended feature for textdomain separation shows at dropdown box Textdomain the pre-selected primary textdomain.
All other additional contained textdomains occur at the source but will not be used, if not explicitely supported by this component!
Please contact the author, if some of the non primary textdomain based phrases will not show up translated at the required position!
The Textdomain default always stands for the WordPress main language file, this could be either intentionally or accidentally!

Warning Messages

If you get warnings either at the overview page or at the editor page, somethings is wrong within the analysed component. The overview page will show warnings, if the textdomain can not be found clearly. In this case the author has written the components code in a way make it hard to detect.

Warnings at the editors view will show up, if the component is using badly coded textdomains. This could be either by integration of other plugins code or accidentally by typing mistakes.

Reported issues are not a problem of Codestyling Localization, it’s caused by the author of the affected component within it’s code.

Regards,

Pedro G.

[Author]

Posts