Hi, we have bought corporate license, we know that v2.0 should be released soon, what we translate now will be kept in 2.0 or the languages strings are changed? if there is new strings added it doesn't matter, what we don't want to find is that we have to start translation from 0 when 2.0 appears.
Regards,
Hi, we have bought corporate license, we know that v2.0 should be released soon, what we translate now will be kept in 2.0 or the languages strings are changed? if there is new strings added it doesn't matter, what we don't want to find is that we have to start translation from 0 when 2.0 appears.
The only notice I can bring on the stage, is that if we find any spelling mistakes or incorrect interpretation, these wording will be fixed, so it should be rewritten in the next version. But it won't be more than 1% of overall system and you'll see the difference in dictionaries that they are not translated.
The only notice I can bring on the stage, is that if we find any spelling mistakes or incorrect interpretation, these wording will be fixed, so it should be rewritten in the next version. But it won't be more than 1% of overall system and you'll see the difference in dictionaries that they are not translated.
Ok, we shouldn't make changes to templates i suppose as this should have a lots of changes, right?
Regards,
You can change templates, but most likely that these changes should be updated with the next big release. In minor releases we try to not change anything critical.
So you either change templates inside theme folder overriding default themes (create your theme following developer manual based on default one) and make changes there and transfer later when updated or do everything within css, images and js
Juan Carlos Celaya wrote:
Ok, we shouldn't make changes to templates i suppose as this should have a lots of changes, right?
Regards,
You can change templates, but most likely that these changes should be updated with the next big release. In minor releases we try to not change anything critical.
So you either change templates inside theme folder overriding default themes (create your theme following developer manual based on default one) and make changes there and transfer later when updated or do everything within css, images and js
Ok, we shouldn't make changes to templates i suppose as this should have a lots of changes, right?
Regards,
You can change templates, but most likely that these changes should be updated with the next big release. In minor releases we try to not change anything critical.
So you either change templates inside theme folder overriding default themes (create your theme following developer manual based on default one) and make changes there and transfer later when updated or do everything within css, images and js
We will wait & work on other things, 2.0 should be released in 1 month approx?
regards,
Stas Kuzma wrote:
Juan Carlos Celaya wrote:
Ok, we shouldn't make changes to templates i suppose as this should have a lots of changes, right?
Regards,
You can change templates, but most likely that these changes should be updated with the next big release. In minor releases we try to not change anything critical.
So you either change templates inside theme folder overriding default themes (create your theme following developer manual based on default one) and make changes there and transfer later when updated or do everything within css, images and js
We will wait & work on other things, 2.0 should be released in 1 month approx?
We don't have exact date, but yes - approximately in 1 month, as we want all previous (tweaked) and new features to work smooth on every environment, so it will take time with QA here, though 80% of what is on the roadmap is completed
We don't have exact date, but yes - approximately in 1 month, as we want all previous (tweaked) and new features to work smooth on every environment, so it will take time with QA here, though 80% of what is on the roadmap is completed
Yes, you can use web interface and see, modify and save translation files.
More information could be found in Languages article in Documentation
Yes, you can use web interface and see, modify and save translation files.
More information could be found in Languages article in Documentation
Yes, you can use web interface and see, modify and save translation files.
More information could be found in Languages article in Documentation
Yes, you can use web interface and see, modify and save translation files.
More information could be found in Languages article in Documentation
Hi, we have bought corporate license, we know that v2.0 should be released soon, what we translate now will be kept in 2.0 or the languages strings are changed? if there is new strings added it doesn't matter, what we don't want to find is that we have to start translation from 0 when 2.0 appears.
Regards,
Hi, we have bought corporate license, we know that v2.0 should be released soon, what we translate now will be kept in 2.0 or the languages strings are changed? if there is new strings added it doesn't matter, what we don't want to find is that we have to start translation from 0 when 2.0 appears.
Regards,
We have modular system, and of course all the translations you create now will be saved in v2.0 version, so no worries about it.
We have modular system, and of course all the translations you create now will be saved in v2.0 version, so no worries about it.
The only notice I can bring on the stage, is that if we find any spelling mistakes or incorrect interpretation, these wording will be fixed, so it should be rewritten in the next version. But it won't be more than 1% of overall system and you'll see the difference in dictionaries that they are not translated.
The only notice I can bring on the stage, is that if we find any spelling mistakes or incorrect interpretation, these wording will be fixed, so it should be rewritten in the next version. But it won't be more than 1% of overall system and you'll see the difference in dictionaries that they are not translated.
Ok, we shouldn't make changes to templates i suppose as this should have a lots of changes, right?
Regards,
Ok, we shouldn't make changes to templates i suppose as this should have a lots of changes, right?
Regards,
So you either change templates inside theme folder overriding default themes (create your theme following developer manual based on default one) and make changes there and transfer later when updated or do everything within css, images and js
So you either change templates inside theme folder overriding default themes (create your theme following developer manual based on default one) and make changes there and transfer later when updated or do everything within css, images and js
regards,
regards,
We don't have exact date, but yes - approximately in 1 month, as we want all previous (tweaked) and new features to work smooth on every environment, so it will take time with QA here, though 80% of what is on the roadmap is completed
We don't have exact date, but yes - approximately in 1 month, as we want all previous (tweaked) and new features to work smooth on every environment, so it will take time with QA here, though 80% of what is on the roadmap is completed
Replies have been locked on this page!