The use of each depends on your choice. If, for example, the text is in front of a field, I think it is better to use the symbol:
In general, you should see if it really needs it or not. You do not have to use it or not. In the text you sent, the first option is more appropriate because the intention is to display a value in front of or below this text
Related Posts:
- WordPress translation loading english file
- Translate arguments of a user added custom code [closed]
- Internationalize plugin so strings can be translated in WPML [closed]
- Custom theme .mo translation file not working
- How to get a translated string from a language other than the current one?
- How to get a localized version of WordPress from a repository?
- Working with l10n contexts (_x etc)
- gettext does not translate when called in ajax
- How to escape the single quote character in i18n translation strings?
- Gettext details
- custom theme: english .mo file not working
- How to escape single and plural i18n text strings?
- Best pratice to make taxonomy terms translatable without changing slugs?
- What are the most used WordPress localization?
- Difference between 2 internationalization (i18n) functions __() & _e()
- How to Translate Contact Form 7 using qTranslate? [closed]
- Localization works but still get “This plugin is not properly prepared for localization” msg in directory
- How to load theme textdomain from plugin?
- Make theme translatable for WPML
- get_the_date() for translating date format
- Should i use _n for pronouns in translation?
- POEdit with Custom mu-plugins code
- How does WordPress choose which translation file to use?
- Using polylang, how can I see which post is the “original” and which are the “translated children”? [closed]
- WPML Translated Term
- Proper way to create / manage gettext (.po, .pot) files?
- WPML custom string translation get outside of container
- _e() function get text_string from function
- Translations not returning translated strings
- Force translated language on front
- Translating dynamic strings
- Easy export/import of data for Translation
- WordPress Theme .mo-file won’t load
- How to become a translator on wordpress.org?
- Translation from .mo file not working in theme
- Localization, escape html elements mid-sentence
- English version of my site show french strings [closed]
- WordPress localization – gettext and git
- How to translate custom Divi module using POEDIT and Polylang [closed]
- Can I set WordPress to display languages based on system language without a plugin?
- /languages/ folder missing in default themes
- How to translate functions.php?
- Can the qTranslateX-Plugin translate non-article text? [closed]
- WordPress Translations
- Post types translation
- WPML language tags (Qtranslate feature) [closed]
- WPML icl_register_string() throws fatal error but works [closed]
- WordPress Translation to french, at -> à not working
- localization of theme and plugins to English (originally in another language)
- String translation for esc_html__() when registering string [closed]
- Making WP theme / plugin multii-lingual without plugins
- Translate string inside twig template
- Interface translation without plugins
- qtranslate loading the wrong language
- WPML admin texts with serialized objects
- Plugin localization persistance (woocommerce)
- WordPress Localization error within return value
- Plugin translation not displaying
- WordPress translation
- Tweak the loop for translation
- Translating form labels shortcode output
- Does WPML translate numbers automatically, or do I have to do the string translation? [closed]
- WPML & Events Manager translatable fields after duplication
- Website Language/Locale Switching
- How to find posts that are missing translation? (wpml)
- .po file is loaded but changes are not appearing
- Handling gettext / string translation when WP is installed in subfolder
- How to create .pot files with POedit?
- Translate a plugin using .po .mo files
- How to make a WordPress plugin translation ready?
- Theme localization of “slugs” (custom post types, taxonomies)
- Override default WordPress core translation
- Different Language for Frontend vs Backend
- Best WordPress Multi-language Plugin? [closed]
- Open Source replacement for WPML? [closed]
- Custom strings for translation using Polylang plugin
- Translate widget titles using qTranslate plugin
- How to print translation supported text with HTML URL
- Localization: I want the backend: english and frontend in defined language
- How-to: Translate plural forms for themes/plugins with PoEdit
- generating po mo translating files from scratch in a wordpress theme
- How to integrate get_post_time with date_i18n function?
- [Plugin WPML] : How to create a translation of a post using the WPML API?
- How to debug failed load_theme_textdomain()?
- How to provide translations for a WordPress TinyMCE plugin?
- How do translated, escaped strings (esc_attr) in Themes work?
- Changing the language of a single page
- what’s different between _x() and _()
- How to handle text with function __(?
- Obtain a list of available translations
- How do I translate: “2 hours and 15 minutes”?
- Disabling Translation Update
- Unknown language json files
- Titles in my sidebar widget appear in all languages – with qtranslate
- How to save a translation of a plugin in “CodeStyling Localization”?
- Set language per post
- List of Default Translated Phrases
- What is the purpose of an extra file for translation?
- How to add extra language packs to WordPress
- load_plugin_textdomain in `plugins_loaded` or `init`?