This post is part of the sub-series on Internationalizing a ClassicPress plugin which is part of the Internationalizing a ClassicPress plugin series.
When internationalizing a plugin, you should, as far as possible, avoid including HTML markup in the localization strings.
Annoyance the First: Thou shalt not put unnecessary HTML markup into the translated string. For example, a heading should…
Continue Reading Ian Grieve’s Article on their blog
Internationalizing a ClassicPress plugin: Don’t include HTML markup in localization
This post is part of the sub-series on Internationalizing a ClassicPress plugin which is part of the Internationalizing a ClassicPress plugin series. When internationalizing a plugin, you should, as far as possible, avoid including HTML markup in the localization strings. Annoyance the First: Thou shalt not put unnecessary HTML markup into the translated string.
Blog Syndicated with Ian Grieve’s Permission
More About This Author
Array
- Dyn365GP2 May 2024New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Allow Lines with Amounts of Zero on Recurring General Journals
- Dyn365GP2 May 2024New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Specify Dimensions on Posted Entries Applications With Realized Gains or Losses
- Dyn365GP1 May 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Understand the Approaches to Configuring a New Company
- Dyn365GP30 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Restore a Deleted Company