Hi, On Wednesday, March 26, 2008 10:02 AM Alexander Wagner wrote: [...] > > Much more important would be how we can configure scid to > > write the code we want. > > Perfectly agree. With a probably not optimal but simple, > good stlye usable without deep knowledg of LaTeX' internals. > Thats what I'd suggest. > > > I'm thinking of the way > > mainline/variations/subvariation/comments etc. are output. > > A config file which scid reads in with a key/value syntax would be > > great, e.g., > > % latex_output.cfg > > Sounds good. One should IMHO just keep in mind that the > defaults has to be set such, that anybody without expert > knowledge can handle it. (Ie. those people arround who just > hit "install latex".)
O.k. but the code should at least be updated to LaTeX2e. And this could be the default behavior and all other customisation is going into a cfg file as proposed. But it depends on the developer(s) of scid wether to modify the TeX export module in such a way. Otherwise we can stop talking at once ;-) Ulrich ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Scid-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
