User talk:Objectivesea

Jump to navigation Jump to search
Getting started
Translation tutorial
How to start
See also
Localisation guidelines
Translating offline

Hi Objectivesea. Welcome to!

You can now start translating.

You should also check the portal for your language, the link is in the sidebar. Other useful pages are linked in the menu next to this message.

Your translations are transferred to the standard product every few days or every few weeks depending on the product. Please notice that it may take longer before you see your translation in the actual product.

It can be just a few days before they appear on Wikipedia, but a few months can pass between each new release of FreeCol.

We wish you a productive and pleasant stay. Please leave any questions on Support. Cheers!


Thread titleRepliesLast modified
Translations110:44, 21 January 2013
Thank you for your contributions to the Esperanto translation of Waymarked Trails!310:21, 21 January 2013


I wrote to you on Transifex. Did you read it?

★ → Airon </sm 09:33, 21 January 2013

Yes. I have now replied. Thank you.

Objectivesea (talk)10:44, 21 January 2013

Thank you for your contributions to the Esperanto translation of Waymarked Trails!

Thank you very much for your contributions to the Esperanto translation of Waymarked Trails! Your translation have been deployed for a while now, and you can see them in action on The only thing that isn't localised is the date and time of update (see upper left) because Django does not have the necessary for Esperanto. There are versions in many other Latin languages though, and if you are interested I can assist in getting a eo into Django.

Guttorm Flatabø (talk)08:53, 21 September 2012

I have made a first attempt at an Experanto file, based on a Brazilian Portuguese version I found at the site you pointed to. I am not an expert on Python syntax, so please let me know if it is acceptable or if additional changes need to be made:

  1. -*- encoding: utf-8 -*-
  2. This file is distributed under the same license as the Django package.

from __future__ import unicode_literals

  1. The *_FORMAT strings use the Django date format syntax,
  2. see

DATE_FORMAT = r'j\-\a \d\e F\, Y' TIME_FORMAT = 'H:i' DATETIME_FORMAT = r'j\-\a \d\e F\, Y\, \j\e H:i' YEAR_MONTH_FORMAT = r'F \d\e Y' MONTH_DAY_FORMAT = r'j\-\a \d\e F' SHORT_DATE_FORMAT = 'Y-m-d' # ISO 8601 SHORT_DATETIME_FORMAT = 'Y-m-d H:i' # ISO 8601 FIRST_DAY_OF_WEEK = 0 # Dimanĉo

  1. The *_INPUT_FORMATS strings use the Python strftime format syntax,
  2. see


'%Y-%m-%d', '%y-%m-%d', # '2013-10-25', '13-10-25'
# '%d-a de %b-o %Y', '%d %b %Y',   # '25-a de okt-o 2013', '25 okt 2013'
# 'la %d-a de %B, %Y', '%d %B %Y', # 'la 25-a de oktobro, 2013', '25 oktobro 2013', 


'%Y-%m-%d %H:%M:%S',     # '2013-10-25 14:30:59'
'%Y-%m-%d %H:%M',        # '2013-10-25 14:30'
'%Y-%m-%d',              # '2013-10-25'
'%y-%m-%d %H:%M:%S',     # '13-10-25 14:30:59'
'%y-%m-%d %H:%M',        # '13-10-25 14:30'

 '%y-%m-%d', # '13-10-25' ) DECIMAL_SEPARATOR = ',' THOUSAND_SEPARATOR = ' ' NUMBER_GROUPING = 3

Objectivesea (talk)01:06, 28 December 2012

Thanks, I'll take a look at this later. Looks good for now.

Guttorm Flatabø (talk)07:48, 2 January 2013