First make sure the language file is found. In your development environment (and only there!) add the following code:
$path = plugin_dir_path( __FILE__ ) . 'lang';
$loaded = load_plugin_textdomain( 'LSample', false, dirname( $path );
if ( ! $loaded )
{
print "File not found: $path";
exit;
}
Then … I would use lowercase text domains only. Not sure if that’s a real issue, but there are some cases where WordPress is setting strings to lowercase automatically. Strings not visible to the end user should stay lowercase.
The po file will not be used, you have to create a mo file after translation. Make sure to click the button. 🙂

Then reload, the strings should be translated now.
Related Posts:
- What is the difference between the .po .mo and .pot localization files?
- How to make a text with hyperlink translatable in WordPress?
- What’s the point on gettext syntax?
- Translate a string to a language with masculin/feminine nouns
- Change locale manually at runtime?
- Text Domains Across Multiple Plugins & Themes
- Can we load “load_theme_textdomain” multiple times with different domains?
- Where are the official i18n WordPress versions stored (SVN)?
- localize inline css
- Can we use a variable hook for language string?
- Locale filter in conjunction with new datepicker localization
- How to use is_rtl with my main style.css?
- Localizing text from XML files
- Localizing strings that come from outside of plugin?
- Alphabetical sorting – local language
- How to detect if text domain is already loaded?
- does a translation (i18n) have to start from an english PO?
- _n() Single and Plural for search results?
- __() with sprintf returns untranslated string
- How to add i18n to a plugin’s Twig template files?
- load_child_theme_textdomain doesn’t work in function.php
- How to prepare SimplePie_Item’s get_date() for l10n?
- The effect of x() family of functions
- How to translate multi-line strings?
- get_locale() behaving strange in same functions.php file
- Do I need the .po file for my plugin?
- WordPress theme with frontend in different language than backend?
- Change WordPress Language
- Strings including html for localisation
- What does the underscore translate function do in my code without a textdoman
- Is it possible to set a different frontend- and backend-language?
- Possibility to use WordPress built-in localization
- Can any users change locale language?
- Localized version offers upgrade to en-us version
- Local WordPress installs don’t verfiy against wp-cli checksum check and how to fix that issue.
- Loading custom language file for plugin
- sprintf bloginfo odditie
- Unable to find where to translate certain tooltip string
- WP core emails translated
- How to translate theme content using site language?
- How can i localized html or php source code from wordpress [closed]
- Setting frontend locale based on postmeta not loading translation
- Using esc_attr function
- Change WordPress language based on user setting
- Define locale WordPress uses with gettext functions?
- Site does not display translations
- Theme doesn’t want to load localization files
- User specified Timezone
- Plugin translation ready – mo file not loaded
- Problem with adding a new post type
- Do I have to use load_plugin_textdomain() or is there any default folder for languages?
- Get localized user roles
- Internationalization of strings with html tags and numbers in WordPress
- Change post date format to hebrew calendar
- failed to open stream: Permission denied warning while load_textdomain
- Requiring Once into plugin PHP File not working
- Where does the locale come from?
- When localizing a theme do I create the .mo and .po
- wordpress localization extending
- How to localize built-in strings in a future-proof manner?
- Is there some ways to autofix the mo or po files instantly?
- I want to dynamically create i18n ecosystem in WordPress
- Language string not detecting used within the function
- Why does my WordPress Upgrade version have a language suffix?
- How to disable gettext feature?
- WordPress in French Language [closed]
- How do I make this plugin translation-ready?
- how to use a default MO file
- Localization of menu items
- Warning: The actual loaded translation content contains mixed textdomains and is not pure translateable within one textdomain
- Is it wrong to use the English version of WordPress to server a site in a different language?
- Hack nav menu to add gettext() to menu items?
- WordPress NavXT plugin localization
- Why is setlocale() returning false on WPEngine?
- WordPress emails translate to French
- How to create some sort of word mapping?
- Is this really always bad? (variables in l10n functions)
- How to change text depending on the country
- How to dynamically change the locale?
- How to show the front end in a different language? I am using the twentytwentythree theme
- i18n: How do I load translations for a language specified in the request?
- Localization works but still get “This plugin is not properly prepared for localization” msg in directory
- Translated strings not appearing – what am I missing?
- Should i use _n for pronouns in translation?
- Why load_textdomain work but not load_plugin_textdomain?
- variables in translatable text
- Using WordPress gettext functions in a library outside plugin or theme scope
- _e() function get text_string from function
- Change locale by detecting viewer’s browser language setting and let them choose prefered language after
- Translating custom post type metaboxes [closed]
- How to Internationalize WordPress – Extract strings with textdomains, per textdomain individually
- Easy export/import of data for Translation
- /languages/ folder missing in default themes
- Internationalize plugin so strings can be translated in WPML [closed]
- Use localized plugin name and description even when the plugin is disabled
- Issue with translation – Gutenberg
- WordPress add_filter to post_date
- Ajax WordPress pass post URLs
- Tweak the loop for translation
- Multi language site using only .mo and WPLANG