To post new answers or open threads, you need to log in. The registration is closed now, sorry. If you are not a member, you are welcome to read the posted content without any limitations. If you have any DAEMON Tools related question, contact our support team.
Please make updates to your current translations and send them via special web form! (so we could update DT Lite 4.11 and include the latest localization files in the next DT Lite build)
it would be nice to have a changelog for the DLL. What is changed, new strings no. 12345-13456 etc
Strings that are already translated shouldn't be necessary to update (in connection with new updates). I don't agree that it would be appropriate or necessary to have a changelog when a new language file comes out. The only thing you have to do is to translate the empty strings, and there's normally not more than 10-15 strings with each new update.
it would be nice to have a changelog for the DLL. What is changed, new strings no. 12345-13456 etc
If you have a Visual Studio or any other resource editor capable of handling unicode message tables you can copy messagetable resource from DLL into a .RC file and compare for changes with any text comparer tool.
I totally agree with this. I was referring when and if strings are changed, corrected, replaced etc.
Thanks,
OJi.
Yes, if existing strings change mentionably (i.e. the meaning/message of the string changes), I agree with you. We would obviously need to be notified of a change that would need our attention. But that said, I neither think nor hope that it will happen. Existing strings should always keep their meaning, and if a string gets obsoleted, it should simply be removed and the string ID not to be re-used.
Imagination is more important than knowledge. --Albert Einstein
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment