Hi Seb, 2009/9/6 Sebastien Lelong <[email protected]>
> Hi Joep, > > > > >> Looks okay and the problems you mention probably can be solved. >> >> > Good. Did you have a look at DITA files (source files), to briefly see > how it's done ? Did you try to write something, maybe with XMLMind XML > Editor (XXE) ? As for me, it required some investment, but once you have it, > it's quite easy to use, maybe even pleasant :) > > I had a brief look at the structure. Did not try it, but are familiar with creating xml documents by hand. Quite easy indeed and unambiguous, but pleasant? ;) > So the only remaining issue (i keep nagging about) is differentiating >> within a chapter for different targets. Like: >> >> * "I wanna try, where are the files ?" >> >> To run this sample, you'll need the last jallib pack (at least 0.2 >> version). You'll also find the exact code we used >> here<http://jallib.googlegroups.com/web/blog_16f88_board_sl_pwm_led.jal> >> . >> * >> >> is a good way to close a tutorial, but this paragraph in each chapter of a >> book becomes annoying. >> > That was just a test, but blog post could be split like this (different > dita files): > > - theory (here, duty, frequency) > - practice > - materials (where are the files ?) > I think we need different introductions, split hardware and software, split main features from all the details, so this will become quite a few files for each blog/topic. Multiplied with the large number of blogs we'd like to have, this will be many, many files... > > As an alternative, as sometime you can see in books, we can specifically > say it comes from a blog. Each chapter (or section, I don't know) is then > authored by someone, explaining the whole. > > For appendix, it's okay to say it is from a blog, but not withinn a 'book'. And if we want to prevent duplication of (similar) documentation, we also need to deal with the difference between the main topics (as used in the tutorials and introduction) and all the gory details (for the full manual). I would suggest an other approach (which probably needs a preprocessor for the dita files). - each chapter is a file, authored by someone. - we define labels for each target, like tutorial, introduction, reference (and a few more, probably 6-8). - in the document we can put xml tags to include or exclude the content for a specific target, e.g. like <include_for_target>tutorial</include_for_target>. I don't know how difficult it is to create such a pre-processor or if it is workable solution for most authors without a major course on jallib document writing... Joep --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" 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/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
