Hi all,I don't know if this would be desirable, but maybe an option to show the little arrow before internal links only once per article should be possible. It might seem unprofessional, or ugly if there are many, many little arrows in the text and they all appear in front of the same word(s) every time they appear in the text (or even worse, if they don't match the name of an article [e.g. [[foo|bar]] produces -->bar, yet there's no [[bar]] article in the collection]. Obviously this can be corrected on the wiki side, before printing, but this kind of automatic style correction would be nice (stripping duplicate links, and not linking if there is great difference between the title of the article and the displayed text).
Best regards, Bence Damokos On Fri, Jan 23, 2009 at 1:02 PM, Volker Haas <[email protected]>wrote: > > Hi Philippe, > > first of all: thanks for your suggestions! We really appreciate any > input - ideas, praise and criticism and ideally patches ;) > > pg wrote: > > (1) customization through code (customconfig.py) is working, but not > > friendly. The file location is ugly. Multiple versions exists > > simultaneously. I suggest to put all customizable vars in a property > > file. I suggest as location $HOME/.mwlib/rl/properties. I suggest a > > very simple and readable format (neither JSON nor XML). An empty or > > absent file implies default values. > > > Regarding the location of the files: > If mwlib.rl is installed using easy_install from pypi the location of > the files is indeed a little ugly (they solely reside in your python > site-packages directory). > But if mercurial is used that should be no problem: customization can be > done in the directory where mwlib.rl is checked out. That directory does > not change even if you upgrade. --> You simply have to edit the config > file in the directory where you checked out mwlib.rl. > > Regarding a different file format for customizations: > That is quite a bit of work - I guess we won't be doing that anytime > soon. I agree that the pdfstyles.py module could be cleaned up a little: > especially the naming of the config variables could be made more > consistent. > > As you suggest below, more configuration options could be added. I > created a ticket at http://code.pediapress.com/wiki/ticket/404 where > ideas can be collected. > > (2) customizable vars. I suggest these (besides those already > > available in customconfig.py) > > .... > > (3) mediawiki vars > > I had to modify the magics.py file to force the visibility of > > mediawiki added variables (those added in LocalSettings.php with some > > code). I suggest to put these in the same property files suggested > > above, with a format familiar to mediawiki writers like > > {{XMOD}} = M3M > > {{XYZ}} = Rescope > > ... > > > I don't really know what we can do in this regard. > > Best, > Volker > > -- > volker haas brainbot technologies ag > fon +49 6131 2116394 boppstraße 64 > fax +49 6131 2116392 55118 mainz > [email protected] http://www.brainbot.com/ > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mwlib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mwlib?hl=en -~----------~----~----~----~------~----~------~--~---
