• How to translate & #187;? Special Characters in HTML. Loco translate issues an error. It’s all about symbol #. How to avoid this? If you are msgid “& #187;” he does not translate it. Or msgid “(text)”. That is, if the text in brackets (). Same.

    • This topic was modified 2 years, 10 months ago by uthvfy.
    • This topic was modified 2 years, 10 months ago by uthvfy.
Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Tim W

    (@timwhitlock)

    How to translate & #187;? Special Characters in HTML.

    See FAQ about HTML in translations:
    https://localise.biz/wordpress/plugin/faqs/html-editing

    Loco translate issues an error. It’s all about symbol #

    What is the error? There is no problem entering # symbols into translations as far as the file editor is concerned. I don’t know of any error that would be issued by Loco Translate in this case.

    Thread Starter uthvfy

    (@uthvfy)

    In the article “HTML In Translations”, I did not emphasize anything for myself. Usually if the .po file is compiled correctly, nothing is displayed in the text field, if somewhere an error, then after restarting the page, this error is displayed in the text field. If the text is taken into the brackets, it will be translated, but this text will appear in the text field which is taken into brackets, that is, for Loco, this is an error, which is not important, round brackets or square, but for some reason it is considered an error, not to mention Already about special characters. If in MSGSTR “” worth # then it will be translated, but it will be displayed in the text field, it means that something is wrong.

    Plugin Author Tim W

    (@timwhitlock)

    I can’t make any sense of this description.

    If you say Loco Translate is producing an error, please show the error.

    My plugin is a PO file editor. If you enter a “#” character and save the file, a “#” will be saved in the msgstr field. I cannot reproduce any issue in doing this. If you can then please demonstrate.

    Thread Starter uthvfy

    (@uthvfy)

    If I write so

    #: wp-includes/formatting.php:98
    msgid “& #171;”
    msgstr “& #171;”

    It translates, but this translation will be displayed in the text box. And this means something wrong. If everything was fine, it would not be displayed.

    Or. I will write so

    #: wp-admin/press-this.php:74
    msgid “The Press This plugin is required.”
    msgstr “Press this”

    all right. If I put brackets () or [ ] [The Press This plugin is required.]

    #: wp-admin/press-this.php:74
    msgid “(The Press This plugin is required.)”
    msgstr “Press this”

    or

    #: wp-admin/press-this.php:74
    msgid “[The Press This plugin is required.]”
    msgstr “Press this”

    It translates, but will be displayed in the editor text field,

    screen https://prom-service.rurs.net/wp-content/uploads/2021/06/1a.jpg

    How to avoid this?

    • This reply was modified 2 years, 10 months ago by uthvfy.
    • This reply was modified 2 years, 10 months ago by uthvfy.
    • This reply was modified 2 years, 10 months ago by uthvfy.
    • This reply was modified 2 years, 10 months ago by uthvfy.
    Plugin Author Tim W

    (@timwhitlock)

    It translates, but this translation will be displayed in the text box. And this means something wrong. If everything was fine, it would not be displayed.

    What you write will be displayed in the editor text field exactly as you write it. What are you expecting it to do?

    Entering the text & #171; will display & #171; this is not a bug.

    all right. If I put brackets () or [ ] [The Press This plugin is required.] It translates, but will be displayed in the editor text field,

    As above. Entering [some text] will show [some text]. I don’t follow how you could expect a string editor to behave any other way.

    Thread Starter uthvfy

    (@uthvfy)

    The fact is that after rebooting the page, the correct translation in the editor will not be displayed. I emphasize, immediately after rebooting. The correct translation is not displayed and the wrong will be displayed.

    Thread Starter uthvfy

    (@uthvfy)

    If there is no error in the .po file, then after rebooting the text editor field will be empty

    Thread Starter uthvfy

    (@uthvfy)

    So, Tim W, the answer will be or not? Or do you prefer not to answer .. And why would Loco write it in the description of your plugin, they say there is such a problem. True better than false, right?

    Plugin Author Tim W

    (@timwhitlock)

    Or do you prefer not to answer

    Your screenshot shows no error. Your descriptions are vague and confusing. You’ve demonstrated no fault and now you’re being rude.

    And why would Loco write it in the description of your plugin, they say there is such a problem. True better than false, right?

    I have no idea what this means.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘file .po’ is closed to new replies.