Translation - Revision history

Drn@ecs.soton.ac.uk: Fixed introduced broken links

2024-07-09T10:30:00Z

Fixed introduced broken links

Drn@ecs.soton.ac.uk: Updated defaultcfg to defaultcfg_zero

2024-07-09T10:28:00Z

Updated defaultcfg to defaultcfg_zero

Drn@ecs.soton.ac.uk: Better to link to API page for bin/export

2022-03-05T12:51:33Z

Better to link to API page for bin/export

Th.lauke@arcor.de: strategy added

2018-08-29T08:48:39Z

strategy added

Th.lauke@arcor.de: some typos and links corrected

2017-01-31T15:19:35Z

some typos and links corrected

Pm705 at 15:18, 8 February 2010

2010-02-08T15:18:54Z

Pm705 at 11:55, 8 February 2010

2010-02-08T11:55:32Z

Pm705 at 11:50, 8 February 2010

2010-02-08T11:50:06Z

Gveranis@gmail.com at 11:52, 29 April 2009

2009-04-29T11:52:30Z

WikiSysop: /* Selecting the session's language */

2007-12-15T12:32:20Z

‎Selecting the session's language

@@ Line 8: / Line 8: @@
 In order to customize EPrints you should make several changes to the configuration files. It is a good time to make yourself familiarize with the  [[EPrints_Directory_Structure/eprints3|EPrints3 Directory Structure]]. Certain files are common for all archives &ndash; <span style="color:red;">change these files only if you ''really'' know what your are doing</span>. Other files are repository specific, any change affects that repository only.
-Repository-dependent files are below [[EPrints_Directory_Structure/eprints3/archives|archives]], each repository has it own substructure. When creating a new repository, configuration files are copied from [[EPrints_Directory_Structure/eprints3/lib/defaultcfg_zero|lib/defaultcfg_zero/]] (or [[flavours/pub_lib/defaultcfg/|flavours/FLAVOUR/defaultcfg/]] if using a [[EPrints flavours|flavour]]). Thus making changes in [[EPrints_Directory_Structure/eprints3/lib/defaultcfg_zero|lib/defaultcfg_zero]] / [[flavours/pub_lib/defaultcfg/|flavours/FLAVOUR/defaultcfg/]] or below will affect all ''newly created'' repositories of that flavour but will have no effect on existing repositories. Probably you want to make certain changes before creating repositories, e.g. adding further languages to [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/lang|lib/defaultcfg_zero/lang]] (and also to [[EPrints_Directory_Structure/eprints3/lib/lang|lib/lang]]), changing the default language and available languages in [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/cfg.d|/lib/defaultcfg_zero/cfg.d/languages.pl]], correcting files in [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/citations|lib/defaultcfg_zero/citations]] and [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/workflows|lib/defaultcfg_zero/workflows]], etc.
+Repository-dependent files are below [[EPrints_Directory_Structure/eprints3/archives|archives]], each repository has it own substructure. When creating a new repository, configuration files are copied from [[Lib/defaultcfg_zero/|lib/defaultcfg_zero/]] (or [[Flavours/pub_lib/defaultcfg/|flavours/FLAVOUR/defaultcfg/]] if using a [[EPrints Flavours|flavour]]). Thus making changes in [[Lib/defaultcfg_zero/|lib/defaultcfg_zero]] / [[flavours/pub_lib/defaultcfg/|flavours/FLAVOUR/defaultcfg/]] or below will affect all ''newly created'' repositories of that flavour but will have no effect on existing repositories. Probably you want to make certain changes before creating repositories, e.g. adding further languages to [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/lang|lib/defaultcfg_zero/lang]] (and also to [[EPrints_Directory_Structure/eprints3/lib/lang|lib/lang]]), changing the default language and available languages in [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/cfg.d|/lib/defaultcfg_zero/cfg.d/languages.pl]], correcting files in [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/citations|lib/defaultcfg_zero/citations]] and [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/workflows|lib/defaultcfg_zero/workflows]], etc.
 In the description below we assume that you've set the repository, and use directories and file names, whenever appropriate, relative to that repository. It should be straightforward to make these changes so that they will have effect for all newly created archives.

@@ Line 8: / Line 8: @@
 In order to customize EPrints you should make several changes to the configuration files. It is a good time to make yourself familiarize with the  [[EPrints_Directory_Structure/eprints3|EPrints3 Directory Structure]]. Certain files are common for all archives &ndash; <span style="color:red;">change these files only if you ''really'' know what your are doing</span>. Other files are repository specific, any change affects that repository only.
-Repository-dependent files are below [[EPrints_Directory_Structure/eprints3/archives|archives]], each repository has it own substructure. When creating a new repository, configuration files are copied from [[EPrints_Directory_Structure/eprints3/lib/defaultcfg|lib/defaultcfg]]. Thus making changes in [[EPrints_Directory_Structure/eprints3/lib/defaultcfg|lib/defaultcfg]] or below will effect all ''newly created'' repositories but will have no effect on existing repositories. Probably you want to make certain changes before creating repositories, e.g. adding further languages to [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/lang|lib/defaultcfg/lang]] (and also to [[EPrints_Directory_Structure/eprints3/lib/lang|lib/lang]]), changing the default language and available languages in [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/cfg.d|/lib/defaultcfg/cfg.d/languages.pl]], correcting files in [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/citations|lib/defaultcfg/citations]] and [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/workflows|lib/defaultcfg/workflows]], etc.
+Repository-dependent files are below [[EPrints_Directory_Structure/eprints3/archives|archives]], each repository has it own substructure. When creating a new repository, configuration files are copied from [[EPrints_Directory_Structure/eprints3/lib/defaultcfg_zero|lib/defaultcfg_zero/]] (or [[flavours/pub_lib/defaultcfg/|flavours/FLAVOUR/defaultcfg/]] if using a [[EPrints flavours|flavour]]). Thus making changes in [[EPrints_Directory_Structure/eprints3/lib/defaultcfg_zero|lib/defaultcfg_zero]] / [[flavours/pub_lib/defaultcfg/|flavours/FLAVOUR/defaultcfg/]] or below will affect all ''newly created'' repositories of that flavour but will have no effect on existing repositories. Probably you want to make certain changes before creating repositories, e.g. adding further languages to [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/lang|lib/defaultcfg_zero/lang]] (and also to [[EPrints_Directory_Structure/eprints3/lib/lang|lib/lang]]), changing the default language and available languages in [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/cfg.d|/lib/defaultcfg_zero/cfg.d/languages.pl]], correcting files in [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/citations|lib/defaultcfg_zero/citations]] and [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/workflows|lib/defaultcfg_zero/workflows]], etc.
 In the description below we assume that you've set the repository, and use directories and file names, whenever appropriate, relative to that repository. It should be straightforward to make these changes so that they will have effect for all newly created archives.

@@ Line 296: / Line 296: @@
 <ul>
 <li>start with an initial tree in any preferred language specified in [[API:bin/import_subjects#The_ASCII_Default_Format|simple format]]
-<li>[[Bin/export|export]] this tree in [[API:bin/import_subjects#The_XML_File_Format|XML format]] via
+<li>[[API:bin/export|export]] this tree in [[API:bin/import_subjects#The_XML_File_Format|XML format]] via
   <tt>~/bin/export <repository_id> subject XML > subjects.xml</tt>
 <li>[[API:bin/import_subjects#SYNOPSIS|import]] the extended version via

← Older revision		Revision as of 08:48, 29 August 2018
Line 289:		Line 289:

	== Subject list ==		== Subject list ==
		+	Unsurprising the subjects have to be translated each.
		+	Thus the GUI (Admin > Config. Tools > Edit subject) is multi-lingual!
		+	Sadly the [[API:bin/import_subjects#The_ASCII_Default_Format\|simple format]] couldn't be used any more, but fortunately the [[API:bin/import_subjects#The_XML_File_Format\|XML format]] isn't that complicated.
		+
		+	For the indispensable format switch
		+	<ul>
		+	<li>start with an initial tree in any preferred language specified in [[API:bin/import_subjects#The_ASCII_Default_Format\|simple format]]
		+	<li>[[Bin/export\|export]] this tree in [[API:bin/import_subjects#The_XML_File_Format\|XML format]] via
		+	<tt>~/bin/export <repository_id> subject XML > subjects.xml</tt>
		+	<li>[[API:bin/import_subjects#SYNOPSIS\|import]] the extended version via
		+	<tt>~/bin/import_subjects <repository_id> --xml --force subjects.xml</tt>
		+	from now on,
		+	</ul>
		+	thus a complete import is part of subject management.

	== Patches ==		== Patches ==

@@ Line 6: / Line 6: @@
 == Multilingual sites ==
-In order to costumize EPrints you should make several changes to the configuration files. It is a good time to make yourself familiarize with the  [[EPrints_Directory_Structure/eprints3|EPrints3 Directory Structure]]. Certain files are common for all archives &ndash; <span style="color:red;">change these files only if you ''really'' know what your are doing</span>. Other files are repository specific, any change affects that repository only.
+In order to customize EPrints you should make several changes to the configuration files. It is a good time to make yourself familiarize with the  [[EPrints_Directory_Structure/eprints3|EPrints3 Directory Structure]]. Certain files are common for all archives &ndash; <span style="color:red;">change these files only if you ''really'' know what your are doing</span>. Other files are repository specific, any change affects that repository only.
 Repository-dependent files are below [[EPrints_Directory_Structure/eprints3/archives|archives]], each repository has it own substructure. When creating a new repository, configuration files are copied from [[EPrints_Directory_Structure/eprints3/lib/defaultcfg|lib/defaultcfg]]. Thus making changes in [[EPrints_Directory_Structure/eprints3/lib/defaultcfg|lib/defaultcfg]] or below will effect all ''newly created'' repositories but will have no effect on existing repositories. Probably you want to make certain changes before creating repositories, e.g. adding further languages to [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/lang|lib/defaultcfg/lang]] (and also to [[EPrints_Directory_Structure/eprints3/lib/lang|lib/lang]]), changing the default language and available languages in [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/cfg.d|/lib/defaultcfg/cfg.d/languages.pl]], correcting files in [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/citations|lib/defaultcfg/citations]] and [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/workflows|lib/defaultcfg/workflows]], etc.
@@ Line 23: / Line 23: @@
    &lt;/ul&gt;
-The template page on other languages should not contain this ''Language'' item as not neccessarily will people recognise it. Rather use a button which reverts the language to English, i.e. insert the following into [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/lang/en/templates|archives/ArchiveID/lang/XX/templates/default.xml]] for all other languages XX except for English:
+The template page on other languages should not contain this ''Language'' item as not necessarily will people recognise it. Rather use a button which reverts the language to English, i.e. insert the following into [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/lang/en/templates|archives/ArchiveID/lang/XX/templates/default.xml]] for all other languages XX except for English:
   &lt;li&gt;&lt;a href="{$config{perl_url}}/set_lang?langid=en"&gt;In English&lt;/a&gt;&lt;/li&gt;
-If you want a little more fancy layout, you might consider using  [http://files.eprints.org/40/ flag images] to be copied to the directory [[EPrints_Directory_Structure/eprints3/lib/static/style/images|lib/static/style/images/flags/]]. If you define a phrase (see the [[#Phrases]] section) of the form "cgi/set_lang:lang_XX" then the set_lang script will use that phrase to render a link to that language. A typical format could be
+If you want a little more fancy layout, you might consider using  [http://files.eprints.org/40/ flag images] to be copied to the directory [[EPrints_Directory_Structure/eprints3/lib/static/style/images|lib/static/style/images/flags/]]. If you define a phrase (see the [[#Phrases|Phrases]] section) of the form "cgi/set_lang:lang_XX" then the set_lang script will use that phrase to render a link to that language. A typical format could be
    <epp:phrase id="cgi/set_lang:lang_hu"><epc:pin name="link">
@@ Line 74: / Line 74: @@
+   }
-here the new phrase "user_preferred_language" should be defined in one of the phrase files (see the [[#Phrases]] section); in it the pin "lang" contains the language itself:
+here the new phrase "user_preferred_language" should be defined in one of the phrase files (see the [[#Phrases|Phrases]] section); in it the pin "lang" contains the language itself:
    &lt;epp:phrase id="user_preferred_language"&gt;Preferred language:
@@ Line 80: / Line 80: @@
    &lt;/epp:phrase&gt;
-<span style="color:red; font-weight:bold">WARNING!</span> While e-mail messages are sent out utf-8 encoded, they are not properly formatted. For non-English e-mails you must apply the "Proper utf-8 encoding for outgoing e-mails" patch from the [[#Patches]] section. Also, by default, the text version of the e-mail does not contain links. This is also corrected by this patch.
+<span style="color:red; font-weight:bold">WARNING!</span> While e-mail messages are sent out utf-8 encoded, they are not properly formatted. For non-English e-mails you must apply the "Proper utf-8 encoding for outgoing e-mails" patch from the [[#Patches|Patches]] section. Also, by default, the text version of the e-mail does not contain links. This is also corrected by this patch.
 === Setting document language ===
-Each document file has its own language. The same document might be submitted in different languages. In the default eprints workflow the reference to the language field is commented out; you only has to enable it. It is in file [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/workflows/eprint|cfg/workflows/eprint/default.xml]], stage "files":
+Each document file has its own language. The same document might be submitted in different languages. In the default Eprints workflow the reference to the language field is commented out; you only has to enable it. It is in file [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/workflows/eprint|cfg/workflows/eprint/default.xml]], stage "files":
   <stage name="files">
@@ Line 131: / Line 131: @@
   </epp:phrase>
-<span style="color: red; font-weight:bold">WARNING!</span> The example above works only after you've applied the "Citation phrases with embedded pins" patch in the [[#Patches]] section.
+<span style="color: red; font-weight:bold">WARNING!</span> The example above works only after you've applied the "Citation phrases with embedded pins" patch in the [[#Patches|Patches]] section.
 == Phrases ==
-Phrase defintions are scattered in several places. There are repository independent ones and repository dependent ones. The latter has preference over the former: if the same entity is defined in both places then the repository dependent definition takes precedence.
+Phrase definitions are scattered in several places. There are repository independent ones and repository dependent ones. The latter has preference over the former: if the same entity is defined in both places then the repository dependent definition takes precedence.
 Phrases are parsed and stored during web server initialization for all repositories. If you make any change in any of the phrase files, you ''must restart'' the apache server to see the effect.
@@ Line 189: / Line 189: @@
 == Other configuration files ==
-Several language-independent configuration files contain hardwired English texts. All of them should be replaced by references to phrases, which, in turn, generate the phrases in all languages. First the list of these files and places, and then two examples of how they can be handled.
+Several language-independent configuration files contain hard-wired English texts. All of them should be replaced by references to phrases, which, in turn, generate the phrases in all languages. First the list of these files and places, and then two examples of how they can be handled.
 *[[EPrints_Directory_Structure/eprints3/lib/citations|lib/citations/saved_search/default.xml]] line 11: &quot;''Untitled search''&quot;
 *[[EPrints_Directory_Structure/eprints3/lib/citations|lib/citations/subject/screen.xml]] line 11: &quot;''Untitled subject''&quot;
@@ Line 241: / Line 241: @@
 <span style="color:red; font-weight:bold; ">WARNING!</span>
-You '''must''' apply the  "Citation phrases with embedded pins" patch in the [[#Patches]] section for this work correctly.
+You '''must''' apply the  "Citation phrases with embedded pins" patch in the [[#Patches|Patches]] section for this work correctly.
 <hr>
@@ Line 304: / Line 304: @@
 === Proper utf-8 encoding for outgoing e-mails ===
-For outgoing e-mails the charset should be "utf-8". The mail headers (From, To, Subject, Reply-To, etc lines) might contain a restricted set of English characters only, other characters should be encoded. This [[EPrints.pm.diff]] [http://files.eprints.org/273 patch file] corrects these, PLUS it enables the URL text from links into the text version, PLUS converts wide characters to bytes (the Net::SMTP perl routine complains).
+For outgoing e-mails the charset should be "utf-8". The mail headers (From, To, Subject, Reply-To, etc lines) might contain a restricted set of English characters only, other characters should be encoded. This [http://files.eprints.org/273 EPrints.pm.diff patch file] corrects these, PLUS it enables the URL text from links into the text version, PLUS converts wide characters to bytes (the Net::SMTP perl routine complains).
 See the tech list references [http://www.eprints.org/tech.php/thread-5762.html 5762],
@@ Line 312: / Line 312: @@
 === Citation phrases with embedded pins ===
-You need to apply the second half of the [[XML/EPC.pm.diff]] patch if want to use citations with embedded pins. See tech list [http://www.eprints.org/tech.php/7236.html 7236].
+You need to apply the second half of the [http://www.eprints.org/tech.php/7236.html XML/EPC.pm.diff] patch if want to use citations with embedded pins.
 === Phrases using the same link twice ===
@@ Line 321: / Line 321: @@
     <epc:pin ref="link">Click here</epc:pin>
   <ep:phrase>
-For both links to work correctly please apply the first half of the [[XML/EPC.pm.diff]] patch. See tech list [[http://www.eprints.org/tech.php/6960.html 6960]].
+For both links to work correctly please apply the first half of the [http://www.eprints.org/tech.php/6960.html XML/EPC.pm.diff] patch.
 === Pluralising depends on language ===
-When invoking a phrase in a citation, the Escript constucts such as <code><epc:if test="..." /></code> or <code><epc print /></code> are not available any more. To transfer pluralising from the citation file into phrases file requires this feature which is achieved by the [[XML/EPC.pm.diff.2]] patch. See tech list [[http://www.eprints.org/tech.php/7300.html 7300]].
+When invoking a phrase in a citation, the Escript constructs such as <code><epc:if test="..." /></code> or <code><epc print /></code> are not available any more. To transfer pluralising from the citation file into phrases file requires this feature which is achieved by the [http://www.eprints.org/tech.php/7300.html XML/EPC.pm.diff.2] patch.
 === Language dependent date and time ===
@@ Line 374: / Line 374: @@
+  }
-== List of files to Translate ==
+== List of files to translate ==
 This was captured from EPrints 3.0.3 - some extra phrase files or .xpage files may appear, but it should give the gist:

@@ Line 1: / Line 1: @@
 [[Category:Contribute]]
-[[Category:Manual]]
+[[Category:Languages]]
 Making translation to Eprints3 is similar to that of earlier versions. Here only some of the differences are pointed out. Also, there is a difference between just translating, or making a multilingual site. If you are making a translation, then with little effort you can also make your site speak English too, a courtesy for casual visitors of your repository.

← Older revision		Revision as of 11:55, 8 February 2010
Line 1:		Line 1:
	[[Category:Contribute]]		[[Category:Contribute]]
		+	[[Category:Manual]]

	Making translation to Eprints3 is similar to that of earlier versions. Here only some of the differences are pointed out. Also, there is a difference between just translating, or making a multilingual site. If you are making a translation, then with little effort you can also make your site speak English too, a courtesy for casual visitors of your repository.		Making translation to Eprints3 is similar to that of earlier versions. Here only some of the differences are pointed out. Also, there is a difference between just translating, or making a multilingual site. If you are making a translation, then with little effort you can also make your site speak English too, a courtesy for casual visitors of your repository.

← Older revision		Revision as of 11:50, 8 February 2010
Line 1:		Line 1:
		+	[[Category:Contribute]]
		+
	Making translation to Eprints3 is similar to that of earlier versions. Here only some of the differences are pointed out. Also, there is a difference between just translating, or making a multilingual site. If you are making a translation, then with little effort you can also make your site speak English too, a courtesy for casual visitors of your repository.		Making translation to Eprints3 is similar to that of earlier versions. Here only some of the differences are pointed out. Also, there is a difference between just translating, or making a multilingual site. If you are making a translation, then with little effort you can also make your site speak English too, a courtesy for casual visitors of your repository.

@@ Line 66: / Line 66: @@
    if( $user->is_set( "lang" ) )
+   {
-        $p->appendChild($session->>make_element( "br" ) );
+        $p->appendChild($session->make_element( "br" ) );
         $p->appendChild($session->html_phrase("user_preferred_language",
                   lang => $user->render_value( "lang" ) ) );

@@ Line 15: / Line 15: @@
    &lt;ul class="ep_tm_menu"&gt;
     &lt;li&gt;&lt;a href="{$config{frontpage}}"&gt;Home&lt;/a&gt;&lt;/li&gt;
-    &lt;li&gt;&lt;a ref="{$config{perl_url}}/set_lang"&gt;Language&lt;/a&gt;&lt;/li&gt;
+    &lt;li&gt;&lt;a href="{$config{perl_url}}/set_lang"&gt;Language&lt;/a&gt;&lt;/li&gt;
      &lt;li>&lt;a href="{$config{base_url}}/information.html"&gt;About&lt;/a&gt;&lt;/li&gt;
     ...
@@ Line 22: / Line 22: @@
 The template page on other languages should not contain this ''Language'' item as not neccessarily will people recognise it. Rather use a button which reverts the language to English, i.e. insert the following into [[EPrints_Directory_Structure/eprints3/archives/ARCHIVEID/cfg/lang/en/templates|archives/ArchiveID/lang/XX/templates/default.xml]] for all other languages XX except for English:
-  &lt;li&gt;&lt;a href="{$config{perl_url}/set_lang?langid=en"&gt;In English&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href="{$config{perl_url}}/set_lang?langid=en"&gt;In English&lt;/a&gt;&lt;/li&gt;
 If you want a little more fancy layout, you might consider using  [http://files.eprints.org/40/ flag images] to be copied to the directory [[EPrints_Directory_Structure/eprints3/lib/static/style/images|lib/static/style/images/flags/]]. If you define a phrase (see the [[#Phrases]] section) of the form "cgi/set_lang:lang_XX" then the set_lang script will use that phrase to render a link to that language. A typical format could be