In that case having multiple XLSs is probably just fine (unless I am misunderstanding). <br><br><div class="gmail_quote">On Thu, Mar 18, 2010 at 8:03 PM, philippe rouxel <span dir="ltr"><<a href="mailto:prouxel.pacte@gmail.com">prouxel.pacte@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Yes, these rules are legal norms electical in my case .<br>
<br>
Thanks for reply.<br>
<br>
2010/3/10 Michael Neale <<a href="mailto:michael.neale@gmail.com">michael.neale@gmail.com</a>>:<br>
<div><div></div><div class="h5">> There is currently no DSL support for decision tables (there is occasionally<br>
> some talk of it, but not sure if it would help this particular case).<br>
> In your case, I would think that in your case you would need to have<br>
> multiple XLS files (you can make them share data I guess, for what is in<br>
> common).<br>
> I gather in your case you have different rules in different languages - not<br>
> the same rules in multiple languages right?<br>
><br>
> On Tue, Mar 9, 2010 at 8:26 PM, philippe rouxel <<a href="mailto:prouxel.pacte@gmail.com">prouxel.pacte@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Hi,<br>
>> I post this, but got no echo:<br>
>><br>
>> My project is multi-national: the business model is in English, but<br>
>> some rules depend on the user's country (fr, de).<br>
>> This rules have to be edited in the locale language.<br>
>><br>
>> For editing a rule, the guided rule editor and a DSL are fine.<br>
>><br>
>> But for a decision table, I did not find a way to use a DSL.<br>
>><br>
>> So, what is the best strategy:<br>
>> + use a template for each DT and loose the benefits of sharing the<br>
>> translation.<br>
>> + use an expander for each DT that parse a DSL and translate the terms.<br>
>><br>
>> Or may be an other solution?<br>
>><br>
>> Regards,<br>
>> Philippe<br>
>> _______________________________________________<br>
>> rules-dev mailing list<br>
>> <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
><br>
><br>
><br>
> --<br>
> Michael D Neale<br>
> home: <a href="http://www.michaelneale.net" target="_blank">www.michaelneale.net</a><br>
> blog: <a href="http://michaelneale.blogspot.com" target="_blank">michaelneale.blogspot.com</a><br>
><br>
> _______________________________________________<br>
> rules-dev mailing list<br>
> <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
><br>
><br>
_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Michael D Neale<br>home: <a href="http://www.michaelneale.net">www.michaelneale.net</a><br>blog: <a href="http://michaelneale.blogspot.com">michaelneale.blogspot.com</a><br>