It is a great benefit to create language-dependent prefixes for use in a multilingual forum environment.
Realisation seems kinda tricky as the standard language packs should better not be touched for prefixes.
So another suggestion needs to think up for such a feature...
- Maybe using a reserved prefix.lang. This prefix.lang may contain some example prefixes and can be filled up with own ones.
- Make the table threadprefixes able to handle multiple prefixes with different translations, e.g. differing by language ID.
[ExiTuS]
I like this idea, to use $lang->
variables in prefix labels. Certainly makes sense to me.
Sorry, I don't like thread bumping at all,
but i like to remind of potential great features to enhance and improve MyBB.
In my initial post I already mentioned some ideas as well as kawaii did, so hopefully some community members will also contribute ideas for a multilingual use of prefixes.
[ExiTuS]
Implementing this feature is not a big deal.
We need to consider and handle potential breakage of existing prefix system as well, along with the existing plugins related to thread prefix. Thats the point to discuss.
I actually really like this idea as well. I wonder if this is best for 1.9 though due to the breaking features and for us to consider how to support current methods to not completely break plugins?
I actually coded a plugin for this years ago. It is kinda easy frankly, simple parse prefix names from the prefix cache at global_start
to replace strings like {prefix:key}
for $lang->prefix_key
A helper function to do this could be useful too (in case the cache is rebuild, for plugins, etc)
(2021-02-25, 09:13 PM)Omar G. Wrote: [ -> ]I actually coded a plugin for this years ago. It is kinda easy frankly, simple parse prefix names from the prefix cache at global_start
to replace strings like {prefix:key}
for $lang->prefix_key
A helper function to do this could be useful too (in case the cache is rebuild, for plugins, etc)
MyBB currently uses the
<lang:...>
format (
https://github.com/mybb/mybb/blob/mybb_1...#L220-L230) for
report reasons and
template groups.
Yes, anyone working on this should make it consistent with current approaches.