<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1456507563708_9305">Hi list,</div><div id="yui_3_16_0_1_1456507563708_9370" dir="ltr">I'm pulling this out of the monster thread because it's something I've been thinking <br></div><div id="yui_3_16_0_1_1456507563708_9378" dir="ltr">about for awhile:</div><div id="yui_3_16_0_1_1456507563708_9386" dir="ltr"><br></div><div id="yui_3_16_0_1_1456507563708_9391" dir="ltr">> Another feature I miss is multi-language comment object. <span id="yui_3_16_0_1_1456507563708_2330" style="line-height:1.5;">Enabling multi-language Help files, even multi-language patch comments can be lot useful!</span></div><br><div id="yui_3_16_0_1_1456507563708_9484" dir="ltr">I'll implement any *clear* spec for multi-language help patches someone comes up <br></div><div dir="ltr">with with the following constraints:</div><div id="yui_3_16_0_1_1456507563708_9694" dir="ltr">1. it separates design from content.</div><div id="yui_3_16_0_1_1456507563708_9695" dir="ltr">2. in only requires documentation writers to care about content.</div><div id="yui_3_16_0_1_1456507563708_9560" dir="ltr">3. it does not pigeonhole help patches into having a single, ugly design</div><div id="yui_3_16_0_1_1456507563708_9559" dir="ltr">4. documentation writers will be guaranteed that whatever they write, it won't <br></div><div id="yui_3_16_0_1_1456507563708_9544" dir="ltr">overlap patch content.</div><div id="yui_3_16_0_1_1456507563708_9542" dir="ltr">5. it is maintainable and scalable<br></div><div id="yui_3_16_0_1_1456507563708_9543" dir="ltr"><br></div><div id="yui_3_16_0_1_1456507563708_9534" dir="ltr">-Jonathan<br> </div></div></body></html>