Forum Discussion
NEW in Rise: Export for Translation
Am I the only one who feels that the bugs and problems reported on this forum systematically seem to be answered by bots? Always the same answer "we will forward to our support", under the understanding that with a little luck a member of the community will bring free solutions. Hey Articulate, your product is a commercial product that you sell expensive, your customers are entitled to get concrete answers to the problems that your product imposes on them. A bug is not a request for functionality to prioritize according to your development backlogs, they are problems to solve all the more quickly as they are blocking for YOUR CLIENTS!!!! The problem described above by Julien has been lying around for months on your forum and has still not been solved. It involves very high manual intervention costs, and for any answer Articulate answers "we are looking into it"??? It's not serious and personally I wonder if we can really continue to recommend Articulate to our customers. Other solutions exist on the market and offer serious support. It would be time for Articulate to rebalance their staff between marketing and developers. The latter must not be very numerous....
BR
a customer for many years but who is at the end of his patience
- MattBradshaw6 years agoCommunity Member
Hi Sven,
No you are not the only one. The issues that Articulate have introduced with the supposed improvement to the translation feature have resulted in a massive amount of manual work for us and a huge translation bill due to previously built-up translation memory being more or less rendered useless.
We've had to give up on the translation feature and gone back to manually duplicating the courses and applying translation section by section.
We are already now looking to move away from Articulate altogether which is a real shame as we've invested a lot of time into the products over the years but the recent issues seem to suggest that they are completely detached from the pressures being experienced in the field.
Thanks,
Matt