<div dir="ltr"><div>Hello, <span style="font-size:14px">Stuart Raeburn,</span></div><div><br></div>Thanks for your email.<div><br></div><div>I update the server and I tried to change the language but the menu was not readable.</div><div><br></div><div>I appended the captured image.</div><div><br></div><div>Thanks.</div><div><br></div><div>Jong-Dae Park</div><div><br></div><div><br></div><div><br></div><div><br><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-05-07 1:00 GMT+09:00 <span dir="ltr"><<a href="mailto:lon-capa-admin-request@mail.lon-capa.org" target="_blank">lon-capa-admin-request@mail.lon-capa.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send LON-CAPA-admin mailing list submissions to<br>
<a href="mailto:lon-capa-admin@mail.lon-capa.org">lon-capa-admin@mail.lon-capa.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://mail.lon-capa.org/mailman/listinfo/lon-capa-admin" target="_blank">http://mail.lon-capa.org/mailman/listinfo/lon-capa-admin</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:lon-capa-admin-request@mail.lon-capa.org">lon-capa-admin-request@mail.lon-capa.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:lon-capa-admin-owner@mail.lon-capa.org">lon-capa-admin-owner@mail.lon-capa.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of LON-CAPA-admin digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: translation of lon-capa (Stuart Raeburn)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 06 May 2015 11:48:47 -0400<br>
From: Stuart Raeburn <<a href="mailto:raeburn@msu.edu">raeburn@msu.edu</a>><br>
To: <a href="mailto:lon-capa-admin@mail.lon-capa.org">lon-capa-admin@mail.lon-capa.org</a><br>
Subject: Re: [LON-CAPA-admin] translation of lon-capa<br>
Message-ID: <<a href="mailto:20150506114847.9wutynpug0c0gwo8@loncapa.org">20150506114847.9wutynpug0c0gwo8@loncapa.org</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";<br>
format="flowed"<br>
<br>
Hi,<br>
<br>
> I want to translate lon-capa web interface into Korean.<br>
> I am looking for a documentation for translation.<br>
<br>
Localization of the LON-CAPA interface for each supported language<br>
uses a file found in /home/httpd/lib/perl/Apache/localize/ on a<br>
LON-CAPA server.<br>
<br>
Below is a description of LON-CAPA's implementation of localization,<br>
which I have copied from the perldoc contained in<br>
/home/httpd/lib/perl/Apache/<a href="http://lonlocal.pm" target="_blank">lonlocal.pm</a> file.<br>
<br>
The <a href="http://lonlocal.pm" target="_blank">lonlocal.pm</a> module itself provides localization services for<br>
LON-CAPA programmers based on the CPAN module: Locale::Maketext. See<br>
"<a href="http://search.cpan.org/~toddr/Locale-Maketext-1.26/lib/Locale/Maketext.pod" target="_blank">http://search.cpan.org/~toddr/Locale-Maketext-1.26/lib/Locale/Maketext.pod</a>"<br>
for more information on Maketext.<br>
<br>
"The internationalization process involves putting a wrapper around<br>
on-screen user messages and menus and turning them into keys, which<br>
the Maketext library translates into the desired language output using<br>
a look-up table ("lexicon").<br>
<br>
As keys we are currently using the plain English messages, and<br>
Maketext is configured to replace the message by its own key if no<br>
translation is found. This makes it easy to phase in the<br>
internationalization without disturbing the screen output."<br>
<br>
I have added a lexicon file for <a href="http://ko.pm" target="_blank">ko.pm</a> to the LON-CAPA CVS repository.<br>
You can retrieve that file from:<br>
<br>
<a href="http://source.loncapa.org/cgi-bin/cvsweb.cgi/~checkout~/loncom/localize/localize/ko.pm?rev=1.1;content-type=text/plain" target="_blank">http://source.loncapa.org/cgi-bin/cvsweb.cgi/~checkout~/loncom/localize/localize/ko.pm?rev=1.1;content-type=text/plain</a><br>
<br>
Currently the <a href="http://ko.pm" target="_blank">ko.pm</a> file contains about 10,000 keys (phrases in<br>
English). As you make translations, you will replace the<br>
corresponding value for each key with the translation of the phrase<br>
used for the key (currently each value is the same as the original key).<br>
<br>
Lexicons for other languages (<a href="http://de.pm" target="_blank">de.pm</a> -- the lexicon for German is the<br>
most complete, and was the one I used to create the initial <a href="http://ko.pm" target="_blank">ko.pm</a><br>
file) can be found at:<br>
<br>
<a href="http://source.loncapa.org/cgi-bin/cvsweb.cgi/~checkout~/loncom/localize/localize" target="_blank">http://source.loncapa.org/cgi-bin/cvsweb.cgi/~checkout~/loncom/localize/localize</a><br>
<br>
If you would like to share your <a href="http://ko.pm" target="_blank">ko.pm</a> lexicon with the LON-CAPA<br>
community that would be much appreciated. If you choose to do that, I<br>
can include the lexicon with future LON-CAPA releases.<br>
<br>
Let me know if you have any questions.<br>
<br>
Thanks,<br>
<br>
Stuart Raeburn<br>
LON-CAPA Academic Consortium<br>
<br>
<br>
Quoting Jong-Dae Park <<a href="mailto:jdpark7@gmail.com">jdpark7@gmail.com</a>>:<br>
<br>
> Hello,<br>
><br>
> I want to translate lon-capa web interface into Korean.<br>
><br>
> I am looking for a documentation for translation.<br>
><br>
> Thanks in advance.<br>
><br>
> Jong-Dae Park<br>
><br>
> Pai Chai University.<br>
><br>
> Daejon, Korea<br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
LON-CAPA-admin mailing list<br>
<a href="mailto:LON-CAPA-admin@mail.lon-capa.org">LON-CAPA-admin@mail.lon-capa.org</a><br>
<a href="http://mail.lon-capa.org/mailman/listinfo/lon-capa-admin" target="_blank">http://mail.lon-capa.org/mailman/listinfo/lon-capa-admin</a><br>
<br>
<br>
End of LON-CAPA-admin Digest, Vol 45, Issue 3<br>
*********************************************<br>
</blockquote></div><br></div>