1. plurk
  2. solace
  3. Issues
Issue #8 new

Seperation of base translation and branding translation.

Atamert Ölçgen
created an issue

There are, naturally, a lot of Plurk and Solace words in the translation. It is perfectly OK to have these in base translation file.

But when branding it would be better not modify the base translations and use another translation file for specific translation strings we want to override.

Therefore I think we should have a project specific translation directory just like a project specific settings file.

Comments (6)

  1. Armin Ronacher

    I would go into the other direction and try to keep the translations unbranded and add branding by changing the templates via theme. Have to discuss that with the rest of the team.

  2. Atamert Ölçgen reporter

    Armin Ronacher: Makes perfect sense. How about this:

    • Some custom template directory setting, such as settings.TEMPLATE_DIRS. Templates in this directory overrides default templates. If a template is missing there default template is used.
    • A setting to supply a complimentary translation file. Which would ideally contain only those translations not in base translations.
  3. Atamert Ölçgen reporter

    I would like to continue working on my solace powered site. But I need to re-brand it. Any suggestions on how I can use a different set of templates while running solace on a repo (and pulling often)?

  4. Atamert Ölçgen reporter

    Themes solve branding problem nicely.

    Currently there are 5 templates that contain the word Solace:

    • kb/overview.html
    • core/login.html
    • users/login.html
    • core/about.html
    • layout.html

    I think we can safely replace Solace with settings.WEBSITE_TITLE except for the last two. about should be overwritten if you want to re-brand and layout.html contains the credit.

    What do you think?

  5. Log in to comment