Comments on: Designer XI 3 New Feature: Translation Manager http://www.dagira.com/2008/10/27/designer-xi-3-new-feature-translation-manager/ ...you are in a twisty maze of passageways, all different... Thu, 09 Sep 2010 09:57:30 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Alex Gory http://www.dagira.com/2008/10/27/designer-xi-3-new-feature-translation-manager/comment-page-1/#comment-888 Alex Gory Tue, 10 Nov 2009 20:10:34 +0000 http://www.dagira.com/?p=127#comment-888 Hi Dave, By cost, I was talking about the time spent to perform the translation... You have to go through any single name, description,... I wonder if someone already did it... Hi Dave,

By cost, I was talking about the time spent to perform the translation… You have to go through any single name, description,…
I wonder if someone already did it…

]]> By: Dave Rathbun http://www.dagira.com/2008/10/27/designer-xi-3-new-feature-translation-manager/comment-page-1/#comment-887 Dave Rathbun Tue, 10 Nov 2009 16:26:57 +0000 http://www.dagira.com/?p=127#comment-887 Hi, Alex, I personally have not tested the translation manager. In theory I get how it works and how it solves a need. But I have not had the opportunity to investigate what sort of overhead it brings. I'm not sure if that's what you meant by "cost" or if you were literally talking about the cost of getting the names and other attributes translated... Hi, Alex, I personally have not tested the translation manager. In theory I get how it works and how it solves a need. But I have not had the opportunity to investigate what sort of overhead it brings. I’m not sure if that’s what you meant by “cost” or if you were literally talking about the cost of getting the names and other attributes translated…

]]> By: Alex Gory http://www.dagira.com/2008/10/27/designer-xi-3-new-feature-translation-manager/comment-page-1/#comment-878 Alex Gory Fri, 06 Nov 2009 15:10:33 +0000 http://www.dagira.com/?p=127#comment-878 Hi all, I've briefly tested the Translation Manager and I suspect 2 major drawbacks : 1) Dave, as you say in your first paragraph : "The data itself is not translated by this tool". There's no help for the translation... when it would be VERY helpful. Even a simple "word for word" translation would be appreciated. 2) The cost in translation then maintenance seems very heavy... Do you agree ? Is there anything I missed ? Hi all,

I’ve briefly tested the Translation Manager and I suspect 2 major drawbacks :
1) Dave, as you say in your first paragraph : “The data itself is not translated by this tool”. There’s no help for the translation… when it would be VERY helpful. Even a simple “word for word” translation would be appreciated.
2) The cost in translation then maintenance seems very heavy…

Do you agree ? Is there anything I missed ?

]]> By: Alan http://www.dagira.com/2008/10/27/designer-xi-3-new-feature-translation-manager/comment-page-1/#comment-454 Alan Thu, 04 Dec 2008 14:46:44 +0000 http://www.dagira.com/?p=127#comment-454 Thanks Dave. I see what you are saying. Hopefully BO will agree that Custom Languages would be a great addition. Thanks Dave. I see what you are saying. Hopefully BO will agree that Custom Languages would be a great addition.

]]> By: Dave Rathbun http://www.dagira.com/2008/10/27/designer-xi-3-new-feature-translation-manager/comment-page-1/#comment-453 Dave Rathbun Thu, 04 Dec 2008 02:32:37 +0000 http://www.dagira.com/?p=127#comment-453 Hi, Alan, I don't know if this would be easier or not. What you would have to do is set up a custom class (or classes) that are unique to each client or location. Suppose that Client A wants to call something "Region" and Client B wants to call it "District" and the default object is called "Area" instead. Your universe would have a special class for Client A where they have an object called Region that is built as @Select(Class\Area). Client B would have a special class where their object District is also made with @Select(Class\Area). Then you would have to include security rules so that each client sees only their classes and no others. It's messy. :) I don't think I would really want to do it that way. Plus your reports would use the source object Area and not the custom renamed object, whereas with your SDK solution you are not breaking any reports. I'm holding out for custom languages. 8-) Hi, Alan, I don’t know if this would be easier or not. What you would have to do is set up a custom class (or classes) that are unique to each client or location. Suppose that Client A wants to call something “Region” and Client B wants to call it “District” and the default object is called “Area” instead. Your universe would have a special class for Client A where they have an object called Region that is built as @Select(Class\Area). Client B would have a special class where their object District is also made with @Select(Class\Area). Then you would have to include security rules so that each client sees only their classes and no others.

It’s messy. :) I don’t think I would really want to do it that way. Plus your reports would use the source object Area and not the custom renamed object, whereas with your SDK solution you are not breaking any reports.

I’m holding out for custom languages. 8-)

]]> By: Alan http://www.dagira.com/2008/10/27/designer-xi-3-new-feature-translation-manager/comment-page-1/#comment-452 Alan Wed, 03 Dec 2008 22:26:54 +0000 http://www.dagira.com/?p=127#comment-452 Hey Dave, I'm curious about your last paragraph "Today you can do this with the @Select() function...". Can you elaborate a little more on that? We've got a batch process running the Designer SDK to do a bunch of renames on the universe to handle these custom names. I'm looking for an easier way to accomplish that. Hey Dave, I’m curious about your last paragraph “Today you can do this with the @Select() function…”. Can you elaborate a little more on that? We’ve got a batch process running the Designer SDK to do a bunch of renames on the universe to handle these custom names. I’m looking for an easier way to accomplish that.

]]> By: Charles http://www.dagira.com/2008/10/27/designer-xi-3-new-feature-translation-manager/comment-page-1/#comment-396 Charles Fri, 31 Oct 2008 09:37:46 +0000 http://www.dagira.com/?p=127#comment-396 This is going to be a valuable feature for us here in Europe. We'll be able to deploy the same univer in English, french, Italian etc. We'll also be able to create American versions :-) This is going to be a valuable feature for us here in Europe. We’ll be able to deploy the same univer in English, french, Italian etc. We’ll also be able to create American versions :-)

]]>