Browsing Albanian translation

25.

Language-choice form

26.

There is more that can be translated (<strong>{1}</strong> {1|record|records}). We only looked up the highest priority <em>{2}</em> records that have not yet been translated or have outmoded (broken) translations.

27.

There is nothing that needs translating.

28.

<p>Use this screen to translate content:</p><ul><li>Things that have not yet been translated at all (and not edited in {1} either) are given empty boxes for you to type translations in.</li><li>Things that need re-translating (because the original text has since been edited) are pre-populated with the existing outmoded translation.</li></ul><p>To re-translate content use the &lsquo;Translate website content&rsquo; footer links from the individual screens featuring that content &ndash; this will bring up a contextual editing form.</p>

29.

There is quite a lot to learn to do translation properly. Make sure you read the <a target="_blank" title="translation tutorial: (this link will open in a new window)" href="http://ocportal.com/docs/tut_intl.htm">translation tutorial</a> carefully. Consider using <a target="_blank" title="Launchpad: (this link will open in a new window)" href="{1}">Launchpad</a>, so that you and other's can work together. ocPortal can <a href="{3}">export <kbd>po</kbd> files for Launchpad</a>, if you have made translations locally. <kbd>po</kbd> files from Launchpad can be used directly in ocPortal: place the <kbd>po</kbd> files in the <kbd>lang_custom/{2}</kbd> directory after deleting any <kbd>lang_custom/{2}/*.ini</kbd> files (obviously only do this if you have already sent any changes you have made up to Launchpad). Many people like to work from inside ocPortal to get direct results, often using the "Translate/re-phrase the software" in the developer tool dropdown in the footer to translate screens individually; but Launchpad allows sharing and has much more powerful editing features.

30.

Sorry we cannot criticise the base language (English), as this is the reference point we use for comparisons.

31.

{1} (<strong>{2}/{3}</strong> {3|string|strings} translated}

32.

You are currently selected to be using <strong>{1}</strong>. Content you add will be saved against {1}, but available in all languages. For it to be properly translated the website staff will need to process it via the content translation queue.

33.

You are currently selected to be using <strong>{1}</strong>. Content you add will be saved against {1}, but available in all languages. We would actually advise that you <a target="_self" href="{3}">switch to {2}</a> (the default website language) to add this content, and then you perform any translations from the &ldquo;translate website content&rdquo; option in the website footer.

34.

You are currently selected to be using <strong>{1}</strong>. Content you edit will be saved against {1}, but your changes will not be applied to any pre-existing translations. Instead those translations will be marked outdated and come up for re-translation in the content translation queue which the website staff will have to process. We would actually advise that you <a target="_self" href="{3}">switch to {2}</a> to make this edit, and then you perform any translations from the &ldquo;translate website content&rdquo; option in the website footer.