[NEW-FEATURE] Implement use of resx for translation of PLC strings #144
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #143
This PR adds the possibility of translation of twin project texts
[breaking] the
ixc
now createscsproj
files with names that comply with C# identifier requirements (due to resx generator using the project name by default to generate resources) files with name using '-' will now use instead '_' (e.g. ax-blazor-example.csproj will be ax_blazor_example.csproj).ixr when no parameter provided will use current directory (ax) as the source (-x) and will retrieve the information about the output project from 'AXSharp.config.json' file. Providing output parameters will not alter the content of config file.
resource identifier creator was moved to
AXSharp.Connector
to share the same logic when creating and searching identifiers.ixc now adds reference to assembly resources for plc string translation. We create new class
PlcTranslator
for each assembly (twin project) that providesResources.PlcStringResources
as default resource for given assembly. All members that can contain data eligible for localization reference the singleton of this 'PlcTranslator'.updates docfx to 2.64.0