Replies: 3 comments 4 replies
-
Thanks for working on this! Yeah, tools was a bit of a mish-mash, and could perhaps be split up more. The original intent was for each module to remain as separate from the others as possible. The log viewer was actually written by someone else. For Tools, I would have a single language file to keep it consistent with the original intent. And then a single Bonfire language file for all of the common strings is perfect. |
Beta Was this translation helpful? Give feedback.
-
OK, so I guess I have your permission to rename Logs.php to Tools.php and update it with new strings... Also please see my latest commit - I wonder if the solution I presented for translating table heading column names that are originally derived from DB table fields is acceptable. |
Beta Was this translation helpful? Give feedback.
-
Just approved and merged that one. And yes, your suggestion works! |
Beta Was this translation helpful? Give feedback.
-
I am working on improving localization of Bonfire. And I am thinking of the proper way to do that.
The strings from themes should obviously go to the general Language/en/Bonfire.php language file. So should perhaps the most common button names and messages - those that are repeated across the modules.
Then, each module should have it's own language files.
But I got stuck with Tools. What was uncommon - I found one language file there already, Logs.php language file. So, should there be a separate language file for Logs, SystemInfo, and also a separate file for the more general stuff (residing in the Module.php file)? So, three files for one module?
This fragmentation got me thinking that perhaps there should only be one language file for all of the Bonfire...
Could @lonnieezell drop a comment here?
Beta Was this translation helpful? Give feedback.
All reactions