##// END OF EJS Templates
upstream » kallithea
RSS

Clone from https://kallithea-scm.org/repos/kallithea

follow Python conventions for boolean values...
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'.
marcink - - Load All Authors

File last commit:

r2577:4857ed50 beta
r3625:260a7a01 beta
Show More
how_to
29 lines | 891 B | text/plain | TextLexer
/ rhodecode / i18n / how_to
History | Annotation | Raw |Copy content |Copy permalink
##########################
# 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