Warning: Declaration of Mfields_Walker_Taxonomy_Dropdown::start_el(&$output, $term, $depth, $args) should be compatible with Walker::start_el(&$output, $object, $depth = 0, $args = Array, $current_object_id = 0) in /home/vssrvorg/public_html/wp-content/plugins/taxonomy-widget/taxonomy-widget.php on line 0
Translating content on the site | Vasudeva Server Help Pages

On multilingual sites, there is often text on the site that needs to be translated. We have created a file with all this text – basically, you need to get it from us, modify it and send it back to us.

How to edit the translation file

The file contains a lot of text like this

msgid “Results”
msgstr “”

Place your translation in between the “” in the msgstr line, so it looks something like this

msgid “Results”
msgstr “Resultamundo”

(Resultamundo is the translation in a language we made up)


  • If there are words that begin with ! or a @, leave those words, but translate the rest of the phrase. These are ‘placeholder’ words that might contain different text depending on the page. Example:msgid “This is the @book-number book that Sri Chinmoy has written since he came to the West, in 1964.”
  • If a phrase contains HTML – for example <em>italics</em>, <strong>bold</strong> or line breaks <br> – then leave the HTML intact when translating the line. If you are not familiar with HTML then scroll down to the section on HTML below.
  • Any lines beginning with # are just comments and you can ignore them. For example:
    #: template.php:39;89
  • Sometimes there is also a ‘msgcxt’ line, it can be left alone. It is just there to tell you where the text will be used in case there is some confusion.
  • See note below on ‘translating’ links to other pages

After the file is finished

Once the file is translated, you can send it to us and we will take it from there!!!!

Translating URL links

In the translation file, you can customise where the URL links to other pages can go to. Most likely, you will want them to point somewhere different than what is specified in the file.

  • The best is if there is a version of the page on your country site
  • The next best thing is to point to another page on your country site that is also relevant to topic. If needed, you can adjust the description text that accompanies the URL too, it doesnt have to be an exact translation
  • Failing that, you could just point to the relevant English page, or to another page in your language on another site. Neither of these are particularly good solutions, but are better than a broken page.
  • If you are linking to a page outside your language site, you need to specify the full URL https://name.org/path . This applies also if you are linking to a page on the main SriChinmoy.org site; you need to specify the URL as https://www.srichinmoy.org/path

Dealing with HTML tags

HTML is the coding language that web pages are made of. You definitely dont need to know about HTML to do the work. But a few of the texts, we found it convenient to keep the some simple HTML there.

We use 3 simple HTML tags:

  1.  If you see something like <strong>some text</strong>, that means the text in between <strong> and </strong> will be rendered in bold
  2. If you see something like <em>some text</em>, that means the text in between <em> and </em> will be rendered in italics
  3. And <br /> will cause a line break – this is often used in poems or aphorisms

So in order to keep the bold, italics and line breaks in your translation, you should keep the HTML tags.