We should consider postponing localization until the last possible moment, typically client side. This means that any elements, arrays, etc, being assembly and relayed from server to client need to potentially identify the string table keys, as well as any format arguments necessary to fill in the requisite gaps.
We will also need to be careful of the scope for this one, and we cannot guarantee concerning consistency throughout the framework. Concerning missions, recently done, in particular, in retrospect, we were not especially careful of this to begin with laying the groundwork for a robust missions module, so much of the rendering is server side. However, it should not be terrible to shift that responsibility to client side.
Other modules, cannot promise the same. Just be careful with it.
Basic Information
Mission version:
0.98.dev-s12
Map used: AltisIndividual Things
We should consider postponing localization until the last possible moment, typically client side. This means that any elements, arrays, etc, being assembly and relayed from server to client need to potentially identify the string table keys, as well as any format arguments necessary to fill in the requisite gaps.
We will also need to be careful of the scope for this one, and we cannot guarantee concerning consistency throughout the framework. Concerning missions, recently done, in particular, in retrospect, we were not especially careful of this to begin with laying the groundwork for a robust missions module, so much of the rendering is server side. However, it should not be terrible to shift that responsibility to client side.
Other modules, cannot promise the same. Just be careful with it.