I have a commercial subscription, but I don't have access to the source code, so I can't do the Hungarian translation. I can get the result of 'abp translate -c hu'. When I am done with the translation, I would send it back and it is possible to integrate the Hungarian language into the commercial section.
Ok, Thank you.
I want to see documentation at both Entity and EntityDTO.
This helps development (at least for me). Where I use the property, VS displays the documentation for it.
Example:
/// <summary>
/// Own accounting system reference
/// Used when the account number is recorded differently in your own system
/// </summary>
public virtual string OwnReference { get; set; }
It would be a good feature if I could also provide the documentation for the properties. (Summary block)
Is such a development expected?
The end result could be similar:
/// <summary>
/// Invoice Issue Date
/// </summary>
public virtual DateTime IssueDate { get; set; }
Hi
I know this command, but it is not the answer to my problems. This is not a solution to the flag problem. It is not localized in the other indicated locations (for either language). It doesn't help with commericial modules, I don't have source code. The translation is complete in the database.
I tested the Blazor project on a commercial version. I'm at a Hungarian localization, where I experience the following errors:
Settings:Account:TwoFactor:Two factor Behavior values are not localized. Paginator are not localized
In the upper right corner, Log In is not localized.
IdentityManagement:OrganizationUnits:Members:Filter are not localized
Hungarian (hu) flag cannot be selected.
Can I submit translations? Where and in what format? It would be a good export / import function, because I could start the translation again for a new project.