1
0
mirror of https://github.com/Jermolene/TiddlyWiki5 synced 2024-11-05 17:46:19 +00:00
Commit Graph

18 Commits

Author SHA1 Message Date
Jermolene
cf4eed0129 Add first pass at a tag manager
As independently suggested by @Skeeve and @Spangenhelm
2014-02-25 20:14:16 +00:00
Jermolene
e5103c32f3 Move command documentation into the core 2014-02-25 14:50:37 +00:00
Jermolene
b0394f1560 Add support for utils-node modules that are only run under Node.js 2014-02-23 22:57:25 +00:00
Jermolene
9e0f1240c5 Change SiteTitle/SiteSubtitle into $:/SiteTitle and $:/SiteSubtitle
To make things more consistent
2014-02-22 11:39:18 +00:00
Jermolene
4ee277f41b Fix some missing translateables 2014-02-21 14:27:49 +00:00
Jermolene
e3c1906eaf Make the show/hide editor button be translateable
Missed by accident from earlier commit
2014-02-20 17:53:23 +00:00
Jermolene
921ff6ae39 Make palette editor translateable 2014-02-20 16:07:03 +00:00
Jermolene
d21fb85d94 Change .tids file extension to .multids
Hopefully less confusing
2014-02-20 10:27:02 +00:00
Jermolene
d00a82e9e9 Put language files in alphabetical order 2014-02-17 08:58:53 +00:00
Jermolene
3307604130 Make type information translateable 2014-02-16 19:58:53 +00:00
Jermolene
1ff8d225d9 Rejig the control panel to use nested tabs for Appearance and Advanced 2014-02-16 19:33:18 +00:00
Jermolene
489509c810 Add missing field descriptions 2014-02-16 19:11:11 +00:00
Jermolene
df8ff9eb26 Make the control panel "internal" tab translatable 2014-02-16 19:02:24 +00:00
Jermolene
e051eb7d90 Making more things translateable
Now we’re done with the text that lives in tiddlers, and we’ll need to
get on with the text that is embedded in code modules.
2014-02-16 09:46:43 +00:00
Jermolene
5a45fffa9e Get the remaining core control panel tabs prepared for translation
We’ll do ThemeTweaks separately as it’s part of the Vanilla theme
2014-02-15 13:29:24 +00:00
Jermolene
a763610db1 Get rid of the separate language prompt tiddler
More consistent to stick with .tids files
2014-02-15 11:36:00 +00:00
Jermolene
c43cd325ca Reduce the inconsistent use of "language" vs. "lingo"
Now we’re just using the word “lingo” for the macro defined in
PageTemplate (where the abbreviation is useful), and using the full
word “language” everywhere else.

It’s possible that we should be using “locale” instead of “language”,
what do you think?
2014-02-15 11:32:11 +00:00
Jermolene
daa79a8612 Move the en-GB language plugin into the core
We need to have the default language baked into the core so that we
don’t have problems if no language plugins are available.
2014-02-11 13:20:17 +00:00