On Mon, Oct 25, 2004 at 05:15:39PM +0300, Martin Vermeer wrote: > > I still feel you're making this too complicated :-)
Mais au contraire, mon cher ami. ;-) [This started as an simple answer and ended as a rant. You have been warned... ;-)] ids are attributes that are allowed in every element. What I would to have is a clever and clear way to deal with them. Take the ids for AGU as an example, that we have already discussed. One of the proposal IIRC, was to allow all labels (ids) to appear in the graphical interface, even the automatic. What I propose now is never to include the automatic labels, but to translate from manual to automatic. This is something that lyx can do quite well. Lets assume that your label called 'aha_gotcha' is located on paragraph 151, according to AGU you should always use 'para151' to refer to that lable, except if you add another paragraph before where it should be 'para152'. The problem for us humans is that those references are not stable, it is easy to refer to them as 'aha_gotcha'. LyX always know where the label appears, so it is easy for it to do that convertion automatically for the user. Now I would like to have a mini-language to put all this knowleadge in the textclasses, the same we do with those $$i, $$o, $$b in the converter stuff. I don't want something that only works for AGU, I want something that works for any XML based format. Have I been clear regarding my motivation? :-) > -- > Martin Vermeer <[EMAIL PROTECTED]> The question is that we do have several mini-languages around: - the lyx file format; - the textclasses format; - the lyxrc format; - the converters format. The problem is that syntax is nuts for almost all of them. Take the textclass as an example, you cann't do this: LatexParam "lang=\"pt\"" Why? because to do this it would be need to change all the uses of lexrc.next() to lexrx.next(true), this means that \ and " are special characters and should be escaped if used. Problem, if we do that the previous example will work, I tested it, but since latex uses lots of slashes all the configuration files would need to use double slashes, exactly as we do it in C++. Is this acceptable? No, IMO. :-) If we are using a "shell-ish" notation why not go all the way, and add ' to the bunch of special characteres? These are questions that I would like to answer in the next development cycle. My awareness for this issues raised certainly because of lyx2lyx. We talked in the past over using a script language in the configuration files, but I don't even use properly what we have now. :-( -- Jos� Ab�lio Matos LyX and docbook a perfect match. :-)
