Replies: 1 comment 1 reply
-
The camelCased ones are specific to the bootstrap templates and is how the single file re-arranges it's content to render the 5 different variants of the bootstrap and bootstrap-* templates, as depicted on our screenshots page. They are calculated at the top of that template file and are based on the template configuration setting, not dynamic based on user agent: Lines 3 to 5 in 910675c The ALLCAPS ones are assigned to the View and present in all templates. They represent configuration values, or are based on dynamic properties of the server or client, etc. Lines 383 to 417 in 910675c
The paste's and comment's settings are all fetched from the API. There are some server settings that get injected into data-attributes, if present, i.e.: Line 525 in 910675c The JS client enables or disables bits parts of the static HTML as needed, if present. For a custom template, the HTML structure is pretty flexible, just the key id-attributes have to exist and relevant HTML elements within them, e.g. a textarea with id "message": Line 564 in 910675c
Right now only the name option can be used to replace the "PrivateBin" labels in the translations. For any other adjustments you would have to change the relevant messages in all the translation files. During upgrades you would then have to add any newly translated strings on the bottom of your modified translation files - we append new messages there to make it easy to spot new and untranslated messages for the translaters (less relevant now that most of them use the Crowdin UI, where the untranslated messages are automatically flagged). And of course you can add other, untranslated messages in any place of your new template - many instance operators change the footer text blurb, for example. |
Beta Was this translation helpful? Give feedback.
-
Hi.
Developing a template. Just a few quick questions:
Beta Was this translation helpful? Give feedback.
All reactions