17 lines
1.9 KiB
XML
17 lines
1.9 KiB
XML
|
<qandaentry id='&s2.idroot;faq.s1tos2'>
|
||
|
|
<question><simpara>Will there be an S1 to S2 converter?</simpara></question>
|
||
|
|
<answer>
|
||
|
|
<para>Short answer: No.</para>
|
||
|
|
<para>Long answer: Maybe, but we're not going to help make it. The problem is that there's no proper way to convert an S1 style to S2. A converter could be made, with much pain, but it'd generate totally ugly S2 code which ignores all the benefits of S2. The resultant code would be so horrid that the potential migrator from S1 would see it, cry, and never come back to S2, the auto-converted code having left such a rotten taste in his or her mouth.</para>
|
||
|
|
<para>Actually, what we hope will happen is that somebody (or many people) will get inspired and start making new style languages <emphasis>on top of</emphasis> S2, many of which would likely be targetted at the HTML-hacker audience who want a style system more like S1.</para>
|
||
|
|
</answer>
|
||
|
|
</qandaentry>
|
||
|
|
<qandaentry id='&s2.idroot;faq.s2large'>
|
||
|
|
<question><simpara>Why is S2 so large/complex/difficult?</simpara></question>
|
||
|
|
<answer>
|
||
|
|
<para>It's not, really. You're probably just overwhelmed and frustrated, hoping it was like S1 with more support for certain pages. Unfortunately, S1 was a dead-end and couldn't be usefully extended.</para>
|
||
|
|
<para>S2 has more than you'll ever use, but that's not to say the rest of it is a waste. Just because you only speak English, does that mean we shouldn't address the problem of internationalization?</para>
|
||
|
|
<para>S2's been designed to be as easy as possible on both regular users and programmers. Once you start creating/modifying S2 code, you should find it's not so bad. And once you have a wild idea of something you want to do with your style, it'll actually be possible... just consult the S2 core layer reference and figure out how to get what you're looking for.</para>
|
||
|
|
<para>Also, see the last paragraph to the previous question.</para>
|
||
|
|
</answer>
|
||
|
|
</qandaentry>
|