Behdad Esfahbod wrote: > Unfortunately though the problems seem to be much more fundamental than I > thought. Nicolas is right to the point with problems he brings up. I'm not > sure I agree with solutions he proposes though. > can you be more specific? what's wrong with the syntax Nicolas proposed? redundancy? > Alternative solutions, for example, include: > > - Write XSL converters from his proposed simple syntax to fontconfig format, > - Write a GUI / TUI tool to generate fontconfig confs. > talking about GUI, I do have something to share. I wrote a javascript-based program to let users set font orders and get instant feedbacks. You can browse the page at http://wenq.org/cloud/fcdesigner.html#en a variant of the code enumerating local fonts using a flash object can be browsed at http://wenq.org/cloud/fcdesigner_local.html#en hit the [create] button on the top to produce the output, which is the content of ~/.fonts.conf. It does use "invasive" syntax such as prepend/binding=strong, but this can be easily changed. I included default options for Chinese, Japanese and Latin; for the first two, bitmap-priority and vector-priority settings can be chosen from the top menu. Any feedback is welcome (maybe start a new thread?) > The point being: we all know XML is too verbose to write manually. That's by > design though. The solution is to not write it manually... > > Anyway, I'm afraid I can't pay too much attention to this right away as I have > to get back to finishing HarfBuzz and other long overdue projects. > > Cheers, > behdad > > PS. Krzysztof, thanks for contributing to the thread. You said many things > that I wanted to say. > _______________________________________________ > Fontconfig mailing list > Fontconfig@xxxxxxxxxxxxxxxxxxxxx > http://lists.freedesktop.org/mailman/listinfo/fontconfig > > > > _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
