On Mon, Apr 6, 2009 at 5:05 AM, Markus <[email protected]> wrote: > > Hi everybody, > > Since BoltWire has reached 3.xx, I decided to finally improve the > German translation and found some issues. > > 1) Are all those strings in site.language still used? > "clearstamp"? Nope.
> "all actions"? Nope. > "auth"? If it is the auth in "[if auth write]", where is "write" in > site.language? Yes. As for "write", only the function names are translatable, not the parameters. > 2) Some strings seem to be missing. Among them: > "Below are the zones used to create page:" > "help" > "Preview Mode." Ok, thank you. These are all added now. > 3) Lots of text is not translated although a translation is given. > Among them: > "You are currently logged in as:" > "You have been successfully logged in as $1." > "Warning: are you sure you want to delete page:" > "Page test successfully stamped." > "Page test has been deleted." > "Page test already exists." > "Could not rename." > ... Are you saying these messages are in the site.language.de page, but don't get translated properly? These are very tight string replacements so if there is even a space off, they will not work. Maybe you can check to make sure the german language page doesn't have any mistakes. Or see if another language file works for these messages. Italian or something. Also, if they are not site messages (ie, in the message box), it is necessary to have the >> << around the text to be translated. It could be these all fail because they have custom elements in them, like page "test". I'm not sure what is going on, and unfortunately I'm quite behind on BoltWire emails so I can't debug this more right now. Perhaps someone else can look into this. > 4) Some pages are predominantly or completely English and would be > great to be translatable without copying them to the fields. Among > them: > Missing Page-page > undo > changes > data > zones > site > plugins > help > search In these cases it is more likely better to have a custom German action page. Ultimately, I envision very advanced language packs with a backup of language specific pages, mapping of commands/functions/conditions to language equivalents, plus a language file. Perhaps other settings. As for custom action pages, and perhaps mapping however, there needs to be mechanisms to allow multiple languages running on the same site. So a user could select their language and things get customized for them. That would take some advanced coding however, and some new features in BoltWire. The action pages in particular, would be easy enough to do, once we settled on a syntax. Perhaps action-de.edit if it exists. Then action.edit. Or something. > 5) May I ask why "php" is in site.language? :) We use to have a php command/function in the core. It's a plugin now. It's gone now... > 6) Is it already possible to localize URLs? For example: > &action=changes -> &aktion=änderungen Not yet, but I suppose it is something we could look at. We have to decide whether or not we want to do this as a mapping kind of system, or as actual pages, names aktion. I'm thinking the former. It would definitely be easier. Cheers, Dan P.S. Sorry for the delay in getting to these emails. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" 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/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
