On Sat, Jul 3, 2010 at 17:27, Luiz Aquino <aquino.lu...@gmail.com> wrote:
> Now, we need some help!
Is there some coordination to avoid duplicate work? I'll look into
de_DE/AT and although I will not promise anything, all others might
check with me. (... and if somebody else wants to lead german
translation effords just tell me and I'm happy to pass this on.)
Maybe there should be a central i18n wiki page where we collect the
.po files, too?
H
http://wiki.sagemath.org/i18n has a new paragraph for that now.
H
If you want it to be a server-wide setting, you can just add an item
to the ``defaults`` and ``descriptions`` dictionaries in
server_conf.py. Accessing the variable is done by importing the global
notebook (twist.notebook) and calling notebook.conf().
If you want it to be a user-specific setting, you'll have to do a bit
more work. Edit user_conf.py and add a descriptions dictionary and
defauls_descriptions method similar to server_conf.py (the
descriptions dictionary should only contain your new setting, as the
settings in user_conf.py are either unused or hidden (as with next
worksheet id)). Then you'll have to change
sagenb/data/sage/html/settings/account_settings.html and add a {%if
auto_table %}{{ auto_table }}{% endif %} line, similar to that in
notebook_settings.html, and then finally, change twist.py to send
``auto_table`` to the templating engine in SettingsPage.render(),
similar to that in NotebookSettings.render().
I can do the work on the second myself, if needed, given a patch I can
apply to my repository.
> ps.: Before follow step 2., it's a good idea to make a backup of
> sagenb directory.
>
> Reference
> [1] http://www.poedit.net/
>
--
Tim Joseph Dumol
First, great work Luiz!
Second, my thoughts for translation are that we will first get the
i18n working -- just work with one language and make sure we have
everything working. Then we can get an idea of how to merge new
translations and how we will distribute the translations (i.e., will
we distribute .mo files, or have something in the build script compile
them from .po files). After we have that working, then we can ask for
actual translations. Getting everything prepared first before asking
for translations seems like a good idea, since I anticipate we will
get a bunch of translations all at once, since there is a pretty big
global community of Sage users out there, and several people have
already expressed interest in translating.
With some more work, I think we can have the i18n working and several
translations working by the end of summer. Hopefully some students who
are not native English speakers can return to school this autumn and
use Sage in their own language!
(It is interesting that we are doing this now, during the World
Cup...with recent travel, I have watched matches in three
countries...)
Dan
--
--- Dan Drake
----- http://mathsci.kaist.ac.kr/~drake
-------
The problem is that SIMPLE_TEMPLATE is a non-unicode string. Repalce
SIMPLE_TEMPLATE = """<p>..."""
with
SIMPLE_TEMPLATE = u"""<p>..."""
I've done the changes required to make the language settable in the
Account and Notebook Settings pages, with the former overriding the
latter. I'm ready to release a new package with the patch if you could
upload the latest translations with the QUESTIONS dictionary.
--
Tim Joseph Dumol <tim (at) timdumol (dot) com>
http://timdumol.com
This probably is better discussed in the trac ticket. My reply will be there.
def _(message, username=None):
return message
in server_conf.py, user_conf.py and tutorial.py and other similar
places, and use those to mark the strings for translation. I'd be glad
to do so in a while, but I currently have a project that I need to
finish.
--
This line appears to be from
sagenb.notebook.challenge
Have you intentionally enabled a challenge --- e.g., reCAPTCHA or a
simple question --- for account registration? You should be able to
disable or configure it from the admin user's Notebook Settings page.