Poedit translate php variables4/27/2023 You should see this based on timestamps (last update) of files. Rename folder to it_IT (because Italian language code in Osclass is it_IT).Download folder oc-content/plugins/osclass_pay/languages/en_US into your computer/desktop.Let’s say we want to translate Osclass Pay Plugin from English to Italian language. This file will appear in the same location on your computer as. Once you’re done editing, click “File > Save”īy saving, the program will automatically create/update. You may continue to edit strings by repeating the above procedure. You can now define translation at bottom of window in “Translation” box. Click on “Source text” of entry you want to translate (you will see existing translations in “Translation” column right to “Source text”). po file before updating it from source code. po file many not reference to proper folder (source code), in this case go to “Translation > Properties” and in “Source paths” select plugin/theme folder and in “Source keywords” you should have these entries (functions): po file and from top menu select “Translation > Update from source code …”. This is very simple action when using Poedit program (free). Easiest way to fix this is update translation list from source code. if you translated v1.0 and there is v2.0 of plugin/theme already). mo) is missing particular strings or some of them are already obsolete (i.e. Sometimes it happens that language file (.po. en_US, ja_JA, cz_CS, …) Update translations with missing or not actual strings You will need to know proper language code Osclass should use, as all other translations (plugins, themes) will need to use same code. If yes, translation files are located in folder oc-admin/themes//languages/en_US/Ĭreate new language files if they do not existīest way is to copy existing translation files for different language and adjust it to yours. Translations of backoffice should be needed just in case you use different backoffice theme than default one (otherwise contained in core translations). mail.sql – translations of email templates (note you will be able to translate email templates also from backoffice).theme.mo, theme.po – translations of default osclass theme (contains translations of bender & sigma themes). messages.mo, messages.po – translation of flash messages (or any other strings used as message or notification).core.mo, core.po – translations from core files (oc-includes, oc-admin folders).mo file as source of translationsĬore translation pack contains most of files comparing theme/plugins translations. po file is used by translator to translate strings into different language (i.e. pot file available in translation folder as well. It’s responsible for most of the text displayed on the website. This is the actual file used by Osclass and is compiled from the .po file. mo file – binary file (machine readable). mo file (located in same folder with same name). You can download existing Osclass translations here or from Market section in your oc-admin. To completely translate Osclass into new language, it is required to translate files in multiple locations. If you have 1000 translation terms, but max_input_vars is 500 only, translations will save up to limit of 500, others will be lost!Īnyway, large translations may be more comfortable to be done in tools like POEdit (section below). Note: Save translations regularly, set PHP variable max_input_vars to large number, ideally 10000 or more, as each translation object takes at least 1 input. To enter translation section, navigate to International > Translations. mo files or use external program or service. In Osclass 8.1.0 and later, it is possible to translate themes, plugins and Osclass core directly in backoffice, without need to find/allocate.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |