> plugins again (most of them from TiddlyTools), but with the > ImportTiddlersPlugin I see only 3 tiddlers tagged with systemConfig
that's odd... can you provide a bit more details? > Can be plugins rewritten, so that I can override (via a different > tiddler) such a text in it (like in the basic TW)? Yes. In many cases, the same method that is used to translate the TW core can be used to translate plugin-defined text. You simply create a separate "translation tiddler" (tagged with systemConfig), that overrides the default text values assigned by the plugin, *without* modifying the underlying plugin code at all. Note: because plugins are processed in alphabetic order (by title), the translation tiddler's title must come *after* the title of the plugin it overrides. A convenient way to do this is to add a 'language code' suffix (e.g., '_es', '_de', '_ru', etc.) to the tiddler title. In order to translate a given plugin, all of the *user-visible* text within that plugin must be defined in separate variables, so that they can be overridden. For example, for http://www.TiddlyTools.com/#GotoPlugin, you could add a separate tiddler called [[GotoPlugin_xx]] (where 'xx' is some language code), containing something like: config.macros.gotoTiddler.listHeading='Found %0 matching title %1...'; config.macros.gotoTiddler.searchItem="Search for '%0'..."; (where the actual text is replaced by a suitable translation, of course) Although I've tried to be more pro-active in writing code that is ready for translation (also called "Localization" or "L10N"), not all plugins have been written in such a way that they are L10N-ready, and there has been a certain degree of 'laziness' on my part: it's sometimes simpler to just embed literal text directly into the code, especially during plugin development, and then go back and move the user-visible text to separate variables only *after* the basic functionality has been tested and debugged. Regrettably, once the plugin code is working, this last step doesn't always happen right away, and is sometimes left incomplete until someone actually attempts to translate the plugin and reports difficulties with specific pieces of text. If you identify specific plugins/scripts that are problematic, I will try to clean them up so they are L10N-ready. Unfortunately, it is not always possible or practical to separate *all* the text from the code and sometimes instances of user-visible text can still remain embedded in the code. Even so, it is definitely my *goal* to make every TiddlyTools plugin as L10N-ready as possible, so that they can be more easily translated into lots of different languages while still allowing you to upgrade to get the latest feature enhancements and bug fixes directly from TiddlyTools. enjoy, -e Eric Shulman TiddlyTools / ELS Design Studios --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
