Files @ 260a7a01b054
Branch filter:

Location: kallithea/rhodecode/i18n/how_to - annotation

Mads Kiilerich
follow Python conventions for boolean values

True and False might be singletons and the "default" values for "boolean"
expressions, but "all" values in Python has a boolean value and should be
evaluated as such. Checking with 'is True' and 'is False' is thus confusing,
error prone and unnessarily complex.

If we anywhere rely and nullable boolean fields from the database layer and
don't want the null value to be treated as False then we should check
explicitly for null with 'is None'.
##########################
# to create new language #
##########################

#this needs to be done on source codes, preferable default/stable branches
 
python setup.py extract_messages <- get messages from project
python setup.py init_catalog -l pl <- create a language directory for <pl> lang
#edit the new po file with poedit or any other editor
msgfmt -f -c <updated_file.po> <- check format and errors
python setup.py compile_catalog <- create translation files

############# 
# to update #
#############

python setup.py extract_messages <- get messages from project
python setup.py update_catalog <- to update the translations
#edit the new updated po file with poedit
msgfmt -f -c <updated_file.po> <- check format and errors
python setup.py compile_catalog <- create translation files


###################
# change language #
###################

`lang=pl`

in the .ini file