Re: [docbook-apps] Extend supported output formats
Hi mentors, Jirka: I added some details about how to do the project and change the time schedule to do the PhoneGap and Android applications. I don't have much idea about the work load that will want for each activity. So, if can you have a look at on timeline of the proposal ans give me a feedback, that will be great!. thank you in Advance !. On Thu, Apr 5, 2012 at 9:30 PM, gihan karunarathne gckarunarat...@gmail.com wrote: Hi Jirka , mentors: I created a proposal for this project idea of DocBook and submitted to the melange[1]. So, if you can give me a feedback on it, then I can make it more strong. (I already shared a google-doc copy with Jirka!.) Last days, I was busy with my first internship interview and deadline of AI project. Sorry for being late with submitting proposal. Thank you!. [1]. http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/gihanchanuka/1# -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993 -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
Hi Jirka , mentors: I created a proposal for this project idea of DocBook and submitted to the melange[1]. So, if you can give me a feedback on it, then I can make it more strong. (I already shared a google-doc copy with Jirka!.) Last days, I was busy with my first internship interview and deadline of AI project. Sorry for being late with submitting proposal. Thank you!. [1]. http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/gihanchanuka/1# -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
On 3.4.2012 11:03, gihan karunarathne wrote: I attached a copy[1] of them (also attached a picture. I don't know, is it possible to send attachments) and already shared to the Jirka. Hey devs, I like to have some comments on my design, about its weaknesses, further enhancements, new feature to add, appreciations and any thing to improve it. I think your comments are more help me to do this. I think that design is good and further improvements probably needs to be based on real experience using such application. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Extend supported output formats
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/03/2012 06:01 AM, Jirka Kosek wrote: On 3.4.2012 11:03, gihan karunarathne wrote: I attached a copy[1] of them (also attached a picture. I don't know, is it possible to send attachments) and already shared to the Jirka. Hey devs, I like to have some comments on my design, about its weaknesses, further enhancements, new feature to add, appreciations and any thing to improve it. I think your comments are more help me to do this. I think that design is good and further improvements probably needs to be based on real experience using such application. Indeed it looks promising! David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPexB4AAoJEMHeSXG7afUhf3QH/jdBpcm8CdQWwug0LKoRZ9z7 P21tCNdIcB8yJJT2onrD0D1RQyPOI58ocAY0bPmZhLcvzo1N6kgWOiKq4WpPvyfX sRljTTz9tMgY1Wk0TVduD7Y4K5/PqZDmc97LrsV2D7nnBnGTQ0jM13xbxb3EjjwM gzbkmH8bs9wUA5C3KLRB9tBN10DSJuhjLdHSoFM3YUZ84XW8v7geRmgCMqwp2g6e Lbix3TV8ezJ7rK/EtMU3EvzBfAt5kGG2lx1X6ANtOBfE6C1U6AV12ThL+A1yEQBJ 3npYH9YlPbt9367Ru+wqQapu4FC4QZp7vKs/YDXOtQ/gAwlQ1Z6seqc46AwGobo= =4Ajj -END PGP SIGNATURE- - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Extend supported output formats
Hi David, Jirka : Thank you very much for your comments !. On Tue, Apr 3, 2012 at 8:30 PM, David Cramer da...@thingbag.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/03/2012 06:01 AM, Jirka Kosek wrote: On 3.4.2012 11:03, gihan karunarathne wrote: I attached a copy[1] of them (also attached a picture. I don't know, is it possible to send attachments) and already shared to the Jirka. Hey devs, I like to have some comments on my design, about its weaknesses, further enhancements, new feature to add, appreciations and any thing to improve it. I think your comments are more help me to do this. I think that design is good and further improvements probably needs to be based on real experience using such application. Indeed it looks promising! David As I know, Android uses XML to keep the data and also for store/maintain the structure of the GUI. Each component has an identifier and when java class want to get access into XML they use identifies. So, those identifies are saved in a one common file generated by Android(default) and get access to other XML contents via it. I researched for find a way to view the html content[1] [2] in Android ( according to Jirka said that I can use DocBook xsl into my project). I found that their is class library for html inside android OS. So, I think it can do the html rendering part and show the content which are generated by DocBook xsl. So I have to use those resources in useful manner, implement more effective user interface[3]. I tried for few of Android applications like pdf readers and eBook readers. I try with those in my Android emulator (which is virtual Android phone running on Desktop) and tried to figure out some of missing thing. [1]. http://developer.android.com/reference/android/text/Html.html [2]. http://developer.android.com/reference/android/webkit/WebView.html [3]. http://developer.android.com/reference/android/widget/package-summary.html -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
On 1.4.2012 20:45, gihan karunarathne wrote: Thank you Jirka for your appreciation. I have to submit a proposal for this DocBook idea. So, as I mentioned above I like to implement Docbook support outfut format which developed using phonegap [1] and a Android Application which create apk for DocBook documentations with including some of native support and rich specific multi-tough features. But you mentioned that instead of going though different native formats it's is better to use technology like phonegap. So I need to know that do you think, it isn't necessary to implement in Android because of phonegap can cover Android also ?. (Hope you got my point) Hi, I think that it's too early to decide on particular technology to use. You can write proposal in a more generic way, e.g. support output suitable for use on iOS and Android devices. Later one you can test if PhoneGap is powerfull enough for you needs. If so, you can relly only on it and deliver to all supported platforms: http://phonegap.com/about/features If you will recognize that PhoneGap is not suitable, you will have to develop two applications one for iOS and second for Android. Still you can reuse DocBook generated content like HTML files and support files for ToC and index. Kasun said that it is better to do the implementation in one format and then move to another. Before GSoC announced, according to the idea page it said that 'it is prefer to choose two types'. David also highlight it. So, is it have enough work load to do over summer ? No worries, there are still things to improve in every app. -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Extend supported output formats
Thank you Jirka for your appreciation. I have to submit a proposal for this DocBook idea. So, as I mentioned above I like to implement Docbook support outfut format which developed using phonegap [1] and a Android Application which create apk for DocBook documentations with including some of native support and rich specific multi-tough features. But you mentioned that instead of going though different native formats it's is better to use technology like phonegap. So I need to know that do you think, it isn't necessary to implement in Android because of phonegap can cover Android also ?. (Hope you got my point) Kasun said that it is better to do the implementation in one format and then move to another. Before GSoC announced, according to the idea page it said that 'it is prefer to choose two types'. David also highlight it. So, is it have enough work load to do over summer ? Sounds good, might be you can summarize mains ideas on DocBook GSoC WiKi. Thank you in Advance !. [1]. http://phonegap.com/ -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
On 29.3.2012 22:23, gihan karunarathne wrote: I got bunch of ideas for ToC and index also. I think, it is better to mention those in my application. I add few in here to see your comments on those. Sounds good, might be you can summarize mains ideas on DocBook GSoC WiKi. -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Extend supported output formats
Hi Kasun : Sorry for the late. I've been busy last two days as I told you early. Yes, I agree with you. I also think, David will agree with me. Almost I will developed the Android output format because of I familiar with Android development. Thus DocBook will get the benefit because of my experience. I started to learn Android from scratch before 3 months ago. At that time I don't have any basic knowledge about mobile development. Now I have a great potential on developing Android applications because of my enthusiasm and quick learning ability. So I think, I can quickly adapt to iOS development. If it is necessary to mentioned about other output format in my GSoC application, I like to come up with another output format before dead line of application submission. I highly appreciate your advice !. On Tue, Mar 27, 2012 at 11:47 PM, Kasun Gajasinghe kasu...@gmail.comwrote: Hi Gihan, Seems you are making a good progress. Here I'd suggest you to keep your focus only on Android development during the application. You will have the community bonding period to think about other things when the design you come up with for Android development is not big enough to fit into three months coding period. David will agree on this I believe. Do one thing at a time. Since you are already familiar with Android development, you can make a good progress there. In addition to asking the questions you have, update us time to time about your status if possible. Please keep in mind that I'm not an Android user either. Regards, --Kasun On Tue, Mar 27, 2012 at 10:00 PM, David Cramer da...@thingbag.netwrote: I'd like to clarify here what I had in mind: when you buy a book from O'Reilly or subscribe to the Linux journal, you have the option of getting various formats. For example, you can get an .epub file or a .apk file (or a mobi for Kindle or pdf). The .apk file in this case is basically an ebook but instead of opening an epub reader and then opening the desired epub file, the book appears on your device as an application. When available, I prefer these to epub files, though it may just be that I haven't found an epub reader I like. I find the .apk ebooks to be faster and more convenient for reading books on my phone in odd moments. I don't know anything about these apk files other than that. I'm guessing that they're a lot like epub, but that's just a guess. I can imagine other things you might do with DocBook on Android and those might well be worth pursuing. I'll be interested to hear what you and Jirka come up with, but I wanted to make sure I hadn't confused the issue :-) Thank you !. -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
On 03/29/2012 02:18:13 PM, gihan karunarathne wrote: Hi Kasun : Sorry for the late. I've been busy last two days as I told you early. Yes, I agree with you. I also think, David will agree with me. Almost I will developed the Android output format because of I familiar with Android On Tue, Mar 27, 2012 at 10:00 PM, David Cramer da...@thingbag.netwrote: I'd like to clarify here what I had in mind: when you buy a book from O'Reilly or subscribe to the Linux journal, you have the option of getting various formats. For example, you can get an .epub file or a .apk file (or a mobi for Kindle or pdf). FYI. I don't wish to confuse things but you may wish to look at, or possibly even coordinate with, the dblatex project (http://dblatex.sourceforge.net/). dblatex generates pdf and various ebook formats, I think, and uses TeX and it's friends to do the heavy lifting. (The result looks quite nice, to my inexpert eye.) I'm a bit of a novice here and it's hard for me to tell just how much overlap/compatibility there is between the processing options used by fo and dblatex. It sure would be nice if they were compatible Regards, Karl k...@meme.com Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Extend supported output formats
Hi Jirka : Thank you very much for your explanation about my ambiguities of project idea. I went though all three replies of yours. I saw that your have some magnificent ideas in your mind. Sure, for example output for Android should be application which can be installed as any other application. So that means, output Android application like some thing which is include the content of information which is given by user in xml. So, I'm going to create an application which include tools for easy access to the content (like search..). Yes. I'm very much happy to hear that I've a clear idea about goal of this project since I got attention. Yes. Actually WebHelp could be in theory used directly, but UX of WebHelp will not be very good on small screens. Thus it would be better to create application that will provide its own touch-friendly interface for working with ToC, index and search. Only real content should be displayed using embedded web browser component. Yes, I can imagine what you are talking about. Main feature of this application should be ability to read the what ever content easily. So in small devices, the whole display should dedicate to view content at reading time. Ex: I like to add a feature which is in ubuntu. In Ubuntu-11.10, when I'm in the home folder and if I want to search for a particular file then I can search by simply type on the keyboard. Automatically, Ubuntu OS takes that as a search and show a simple text box which include the word that we are searching for. Also it highlights first best match and navigate to that file. Like wise we can add search content in that way. When user want to search for a particular word, what he has to do is simply start typing word. Or in smart multi-tough phones, motion of finger move (horizontally, vertically or diagonally) will pop up a key board to type. Also it is posibble to use voice recognition system in smart phone to get the input. I got bunch of ideas for ToC and index also. I think, it is better to mention those in my application. I add few in here to see your comments on those. Thank you in Advance !. -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
On 29.3.2012 22:18, Karl O. Pinc wrote: FYI. I don't wish to confuse things but you may wish to look at, or possibly even coordinate with, the dblatex project (http://dblatex.sourceforge.net/). Gihan, please don't look at this project. :-) No seriously it is of no use for your GSoC project. db2latex can generate nice PDFs, but PDF is hard to reflow and not suitable for small screens. -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Extend supported output formats
Hi Jirka : So I think Jirka should conclude the final decision and we should wait until his comments. I'm not sure what you are asking for now. In here, I'm asking from you to make a choice because of you are the one who came up with idea. But finally you give me the key to make a choice. I'm happy about it. In these two ideas, I can see some advantages and disadvantages; 1. Create new document packaging format (something like .epub) and special reader software for it. User will install this reader and then use it to open documents. 2. Package reader software with each documet. Users will just install document as application. In first choice, it may be a generic solution which can use for many different purposes. Also it has some extending capabilities. In a situation like, user want to read two documents which are related to each other simultaneously. So it is possible to implement special reader which can keep track on books(multiple tabs). Also user may not want to be confuse by installing many apps. I think, David is the better person to answer this (because he is engaging with stuff like this). But it may hard to implement. In second choice, it can be easy to implement. Because we embedded every things in building time. May possible to apply different policies on different documents. I'm trying to get in to iOS development[1]. I registered in developer site but unfortunately I can't download their developing tool because of it's a big size of file. I hope to get into iOS soon. These days I'm busy with finishing my Android project[2]. After that I can accelarate my work. Hope Jirka will help me to get though this idea. David, I think by adding iOS also into my work is enough to do over the summer hopefully. I don't think that developing native applications for two platforms is very effective at this stage. If you want to cover more platforms, then you can choose completely different route. Try to create something like WebHelp but with UI suitable for smaller screens and then use PhoneGap to target multiple platforms (http://phonegap.com/). This is a nice idea. We can kill seven birds with one stone (not two). But one thing, I like to mention. It may be not possible to use native support like speech recognition. I don't know more about phonegap, so I need some time to understand its capabilities. As I know, Android becoming more popular than other smart phones. So, it is prefer to develop an application for Android with full of user friendly features with multi-tough and native supports. You should spend more time on researching possible ways to delivering documents with good UX on small devices now. Not only thinking about what can be done, but also looking to existing software like eBook readers, mobile Web and PDF readers. Create lists of features missing in those products and things that sucks. Then you can create list of requirements for your application. After you have this, you should start thinking about possible implementation strategies. As you mentioned above, It will be very good start to understand webhelp. I followed its documentation partially, so I should finish it firstly. So it is good to use phonegap instead of developing for iOS. I like to develop application on phonegap and extend the output formats. I invite you to add some comments for developing an application with using native support of Android !. Jirka,David, Kasun and docbook devs; If you can give some ideas or any comments on this project, its highly appreciate. It will greatly help me to start my GSoC application !. Thank you !. -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
Okay Jirka, that time, I got busy with my friend's Android phone and thinking about new features. I didn't notice about that and just saw your post. On Fri, Mar 30, 2012 at 2:08 AM, Jirka Kosek ji...@kosek.cz wrote: On 29.3.2012 22:18, Karl O. Pinc wrote: FYI. I don't wish to confuse things but you may wish to look at, or possibly even coordinate with, the dblatex project (http://dblatex.sourceforge.net/). Hi Karl : Thank you for your interesting about this discussion even though your support is not applicable here. Gihan, please don't look at this project. :-) No seriously it is of no use for your GSoC project. db2latex can generate nice PDFs, but PDF is hard to reflow and not suitable for small screens.
Re: [docbook-apps] Extend supported output formats
On 03/29/2012 03:38:34 PM, Jirka Kosek wrote: On 29.3.2012 22:18, Karl O. Pinc wrote: FYI. I don't wish to confuse things but you may wish to look at, or possibly even coordinate with, the dblatex project (http://dblatex.sourceforge.net/). No seriously it is of no use for your GSoC project. db2latex can generate nice PDFs, but PDF is hard to reflow and not suitable for small screens. dblatex will also output TeX, which seems to be able to be converted into all sorts of different output formats. I've no idea how to get from here to there, or whether it's a good idea but TeX is for typesetting, a lot different from PDF, and to the uninformed (like me) it sounds like typesetting is just the sort of thing you do to switch between different screen sizes/looks. Karl k...@meme.com Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Extend supported output formats
On 27.3.2012 13:15, gihan karunarathne wrote: Sure, for example output for Android should be application which can be installed as any other application. So that means, output Android application like some thing which is include the content of information which is given by user in xml. So, I'm going to create an application which include tools for easy access to the content (like search..). Yes. Yes, but you will need also some postprocessing step which will take resulting HTML/CSS/image files and pack them together into single package, sometimes together with simple application for viewing content. Do you mean that some thing like webhelp which use XHTML to generate the content from user then include index for built XHTML output and also include search. Do you mean some thing like that ? Yes. Actually WebHelp could be in theory used directly, but UX of WebHelp will not be very good on small screens. Thus it would be better to create application that will provide its own touch-friendly interface for working with ToC, index and search. Only real content should be displayed using embedded web browser component. My problem was, is it possible to run a apk which is not encrypted (as like XHTML-xsl , webhelp-xsl ) and create the structure by using XSLT ?. I never developed Android application myself, but I bet that you can put any additional resources into .apk including HTML/CSS/images. I think, you got me wrong at this point. I told that, is it possible to make apk structure with out using Android compiler. I think it is not possible. Of course, if documentation will be deplyed as .apk it has to be built each time using Adroid SDK or what's the name of this beastie. -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Extend supported output formats
On 27.3.2012 13:48, gihan karunarathne wrote: Can you explain it ? I think that David already gave you answer. But basically you can either: 1. Create new document packaging format (something like .epub) and special reader software for it. User will install this reader and then use it to open documents. 2. Package reader software with each documet. Users will just install document as application. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Extend supported output formats
On 26.3.2012 22:31, gihan karunarathne wrote: I need to understand few thing about the project idea of Extend support out put formats[0]. First, I also need to clarify the idea which is in the idea page[1]; *“Output format packages” output by the DocBook style sheets would be easily consumable / installable by hosting applications.* What does it mean by easily consumable / installable ?. Can you explain further ?. Sure, for example output for Android should be application which can be installed as any other application. Application will contain both simple application for browsing content and content itself. As I understood, the main goal of this project is generating an another type of formats file (ex:Android,iPad) by a XSLTProcessor. So, in order to do that we want xsl style sheet which includes instructions and other directives that guide the processor in the production of the output document, right? Yes, but you will need also some postprocessing step which will take resulting HTML/CSS/image files and pack them together into single package, sometimes together with simple application for viewing content. My problem was, is it possible to run a apk which is not encrypted (as like XHTML-xsl , webhelp-xsl ) and create the structure by using XSLT ?. I never developed Android application myself, but I bet that you can put any additional resources into .apk including HTML/CSS/images. Or do we have to create the common structure according to the Android source code and compile is using Android tools and embedded the DocBook documentation into apk application. Thus we can open it in Android. Also we can use ANT to configure the procedure. What method should I do ? Is there any other successful way to do it ?. I also like to know, what should be the output of DocBook Android_xsl(a name that is made by me) should look like. I mean, what is final goal of this project look like. Output (in case of Android) should be tool (probably Java written, maybe Ant build file will be sufficient) which takes as an input DocBook XML document and proudces Android application which can be installed and after it is installed it can be used for browsing original DocBook document including features like collapsible table of contents, searchable index and full-text searching. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Extend supported output formats
On 21.3.2012 21:14, David Cramer wrote: In the case of building an apk from DocBook, much of the source for the apk will be generated from DocBook at build time. I would look around for some .apk books and see how close the html and other internal resources are to .epub. If a .apk book is very close to .epub, then it should be a pretty easy task to turn the .epub you currently get from DocBook into a .apk file. If that's the case, you would want to find other stuff to add to the proposal so you have enough to do over the summer. I'm far from Android expert (I'm not even user). AFAIK .apk is complete application. Gihan would have to develop Android application for browsing HTML pages produced from DocBook. Of course this is quite simple as Android application can easily include Web browser widget. -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Extend supported output formats
Hi Jirka : I'm very much glad to see the first reply from my mentor on Extend output formats. And also thank you very much Jirka for paying attention about my doubts and give some explanations. I went though your reply. But I found some ideas which are not fully clear to me. On Tue, Mar 27, 2012 at 2:07 PM, Jirka Kosek ji...@kosek.cz wrote: On 26.3.2012 22:31, gihan karunarathne wrote: I need to understand few thing about the project idea of Extend support out put formats[0]. First, I also need to clarify the idea which is in the idea page[1]; *“Output format packages” output by the DocBook style sheets would be easily consumable / installable by hosting applications.* What does it mean by easily consumable / installable ?. Can you explain further ?. Sure, for example output for Android should be application which can be installed as any other application. So that means, output Android application like some thing which is include the content of information which is given by user in xml. So, I'm going to create an application which include tools for easy access to the content (like search..). Application will contain both simple application for browsing content and content itself. For an Android application, I should mostly focus on effectively use of display size and building more user friendly searching mechanism, index page etc.. As I understood, the main goal of this project is generating an another type of formats file (ex:Android,iPad) by a XSLTProcessor. So, in order to do that we want xsl style sheet which includes instructions and other directives that guide the processor in the production of the output document, right? Yes, but you will need also some postprocessing step which will take resulting HTML/CSS/image files and pack them together into single package, sometimes together with simple application for viewing content. Do you mean that some thing like webhelp which use XHTML to generate the content from user then include index for built XHTML output and also include search. Do you mean some thing like that ? My problem was, is it possible to run a apk which is not encrypted (as like XHTML-xsl , webhelp-xsl ) and create the structure by using XSLT ?. I never developed Android application myself, but I bet that you can put any additional resources into .apk including HTML/CSS/images. I think, you got me wrong at this point. I told that, is it possible to make apk structure with out using Android compiler. I think it is not possible. Or do we have to create the common structure according to the Android source code and compile is using Android tools and embedded the DocBook documentation into apk application. Thus we can open it in Android. Also we can use ANT to configure the procedure. What method should I do ? Is there any other successful way to do it ?. I also like to know, what should be the output of DocBook Android_xsl(a name that is made by me) should look like. I mean, what is final goal of this project look like. Output (in case of Android) should be tool (probably Java written, maybe Ant build file will be sufficient) which takes as an input DocBook XML document and proudces Android application which can be installed and after it is installed it can be used for browsing original DocBook document including features like collapsible table of contents, searchable index and full-text searching. I not afraid to tell that you are thinking about some thing like webhelp, is it?. With some changes those should enhance the use of content. If I got some thing wrong, please correct me ?. I can send you a prototype of appearance of the application which I'm going to build, if you wish. Thank you !. -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
Hi Jirka : I'm not clear one thing that you said. On Tue, Mar 27, 2012 at 2:10 PM, Jirka Kosek ji...@kosek.cz wrote: On 21.3.2012 21:14, David Cramer wrote: I'm far from Android expert (I'm not even user). AFAIK .apk is complete application. Gihan would have to develop Android application for browsing HTML pages produced from DocBook. Of course this is quite simple as Android application can easily include Web browser widget. What did you mean by this point?. Am I going to implement a html interpreter(browser) which is showing the HTML pages produced by DocBook? So far I'm with the idea of Android-xsl sheet produces android applications (APKs) for each user xml input(which is in DocBook format). This APK has the capabilities such as collapsible table of contents, searchable index and full-text searching. Ex: if user A wants to build android apk, he can build it by using Android-xsl and install in to Android. Also user B wants an apk, also he should follow previous steps and both have different apk applications for their documents. But I got this point as their is an Android application which can interpret the output from DocBook HTML. Some thing like text editor. But it include the tools which give capabilities such as collapsible table of contents, searchable index and full-text searching. But it is conflict with the point which is said by you earlier(with my previous understanding) : *Output (in case of Android) should be tool (probably Java written, maybe Ant build file will be sufficient) which takes as an input DocBook XML document and proudces Android application which can be installed and after it is installed it can be used for browsing original DocBook document including features like collapsible table of contents, searchable index and full-text searching. * Can you explain it ? Thank you in Advance !. -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka
Re: [docbook-apps] Extend supported output formats
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/27/2012 06:48 AM, gihan karunarathne wrote: Hi Jirka : I'm not clear one thing that you said. On Tue, Mar 27, 2012 at 2:10 PM, Jirka Kosek ji...@kosek.cz mailto:ji...@kosek.cz wrote: On 21.3.2012 21:14, David Cramer wrote: I'm far from Android expert (I'm not even user). AFAIK .apk is complete application. Gihan would have to develop Android application for browsing HTML pages produced from DocBook. Of course this is quite simple as Android application can easily include Web browser widget. What did you mean by this point?. Am I going to implement a html interpreter(browser) which is showing the HTML pages produced by DocBook? Sorry for being out of the thread for a bit. I've been busy over the past few days. I'd like to clarify here what I had in mind: when you buy a book from O'Reilly or subscribe to the Linux journal, you have the option of getting various formats. For example, you can get an .epub file or a .apk file (or a mobi for Kindle or pdf). The .apk file in this case is basically an ebook but instead of opening an epub reader and then opening the desired epub file, the book appears on your device as an application. When available, I prefer these to epub files, though it may just be that I haven't found an epub reader I like. I find the .apk ebooks to be faster and more convenient for reading books on my phone in odd moments. I don't know anything about these apk files other than that. I'm guessing that they're a lot like epub, but that's just a guess. I can imagine other things you might do with DocBook on Android and those might well be worth pursuing. I'll be interested to hear what you and Jirka come up with, but I wanted to make sure I hadn't confused the issue :-) Thanks, David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPcesXAAoJEMHeSXG7afUhzk4IAI6q4lnivS2J0/sXLCelM5Oj LTPtvvFGETEjFNlSsWhin6+QqKoC/GlXgGITJTZGv4fLGnrWm/tNFogRxy8jCEnT Px0ySrybYf82BJqVBTOsfcxWhIU2ELTIlwWPBNB+muuVw92GMOYKxUa8N0IJyP1n JTLKqYymYK0GgEREy0VpzwFJT9cyQbkKWA3gcfRvTDwebnS9v7Y6IROxXgPZDrcl MvHzhNjyiuvh4qA8wRK+5p8B2HFsqILJrhFUU6Ma5y1ScdHZlHnSSHUEiTD7LdPM 8xAon6+xXRUvGdGB1twnZCAoi/RGM52KN/ZT4GB1JDsGA06SfdIo5jaC+dXavDw= =VYwa -END PGP SIGNATURE- - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Extend supported output formats
Hi David, Jirka : It's pleasure to see you in here with some great imagination. Thank you for putting your thoughts at correct place and make my idea more stronger. I think, David is with me and he pointed out some thing similar to my first idea which had in my mind. As I mentioned earlier; *So far I'm with the idea of Android-xsl sheet produces android applications (APKs) for each user xml input(which is in DocBook format). This APK has the capabilities such as collapsible table of contents, searchable index and full-text searching. Ex: if user A wants to build android apk, he can build it by using Android-xsl and install in to Android. Also user B wants an apk, also he should follow previous steps and both have different apk applications for their documents.* So I think Jirka should conclude the final decision and we should wait until his comments. I'm trying to get in to iOS development[1]. I registered in developer site but unfortunately I can't download their developing tool because of it's a big size of file. I hope to get into iOS soon. These days I'm busy with finishing my Android project[2]. After that I can accelarate my work. Hope Jirka will help me to get though this idea. David, I think by adding iOS also into my work is enough to do over the summer hopefully. On Tue, Mar 27, 2012 at 10:00 PM, David Cramer da...@thingbag.net wrote: I'd like to clarify here what I had in mind: when you buy a book from O'Reilly or subscribe to the Linux journal, you have the option of getting various formats. For example, you can get an .epub file or a .apk file (or a mobi for Kindle or pdf). The .apk file in this case is basically an ebook but instead of opening an epub reader and then opening the desired epub file, the book appears on your device as an application. When available, I prefer these to epub files, though it may just be that I haven't found an epub reader I like. I find the .apk ebooks to be faster and more convenient for reading books on my phone in odd moments. I don't know anything about these apk files other than that. I'm guessing that they're a lot like epub, but that's just a guess. I can imagine other things you might do with DocBook on Android and those might well be worth pursuing. I'll be interested to hear what you and Jirka come up with, but I wanted to make sure I hadn't confused the issue :-) Thank you !. [1]. http://en.wikipedia.org/wiki/IOS [2]. http://code.google.com/p/parental-controller-android/ -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
On Tue, Mar 27, 2012 at 11:32 PM, gihan karunarathne gckarunarat...@gmail.com wrote: Hi David, Jirka : It's pleasure to see you in here with some great imagination. Thank you for putting your thoughts at correct place and make my idea more stronger. I think, David is with me and he pointed out some thing similar to my first idea which had in my mind. As I mentioned earlier; *So far I'm with the idea of Android-xsl sheet produces android applications (APKs) for each user xml input(which is in DocBook format). This APK has the capabilities such as collapsible table of contents, searchable index and full-text searching. Ex: if user A wants to build android apk, he can build it by using Android-xsl and install in to Android. Also user B wants an apk, also he should follow previous steps and both have different apk applications for their documents.* So I think Jirka should conclude the final decision and we should wait until his comments. I'm trying to get in to iOS development[1]. I registered in developer site but unfortunately I can't download their developing tool because of it's a big size of file. I hope to get into iOS soon. These days I'm busy with finishing my Android project[2]. After that I can accelarate my work. Hope Jirka will help me to get though this idea. David, I think by adding iOS also into my work is enough to do over the summer hopefully. Hi Gihan, Seems you are making a good progress. Here I'd suggest you to keep your focus only on Android development during the application. You will have the community bonding period to think about other things when the design you come up with for Android development is not big enough to fit into three months coding period. David will agree on this I believe. Do one thing at a time. Since you are already familiar with Android development, you can make a good progress there. In addition to asking the questions you have, update us time to time about your status if possible. Please keep in mind that I'm not an Android user either. Regards, --Kasun On Tue, Mar 27, 2012 at 10:00 PM, David Cramer da...@thingbag.net wrote: I'd like to clarify here what I had in mind: when you buy a book from O'Reilly or subscribe to the Linux journal, you have the option of getting various formats. For example, you can get an .epub file or a .apk file (or a mobi for Kindle or pdf). The .apk file in this case is basically an ebook but instead of opening an epub reader and then opening the desired epub file, the book appears on your device as an application. When available, I prefer these to epub files, though it may just be that I haven't found an epub reader I like. I find the .apk ebooks to be faster and more convenient for reading books on my phone in odd moments. I don't know anything about these apk files other than that. I'm guessing that they're a lot like epub, but that's just a guess. I can imagine other things you might do with DocBook on Android and those might well be worth pursuing. I'll be interested to hear what you and Jirka come up with, but I wanted to make sure I hadn't confused the issue :-) Thank you !. [1]. http://en.wikipedia.org/wiki/IOS [2]. http://code.google.com/p/parental-controller-android/ -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993 -- ~~~***'***~~~ *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com, *linked-in: *http://lk.linkedin.com/in/gajasinghe* * *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org/ * twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg
Re: [docbook-apps] Extend supported output formats
Hi Jirka : I need to understand few thing about the project idea of Extend support out put formats[0]. First, I also need to clarify the idea which is in the idea page[1]; *“Output format packages” output by the DocBook style sheets would be easily consumable / installable by hosting applications.* What does it mean by easily consumable / installable ?. Can you explain further ?. As I understood, the main goal of this project is generating an another type of formats file (ex:Android,iPad) by a XSLTProcessor. So, in order to do that we want xsl style sheet which includes instructions and other directives that guide the processor in the production of the output document, right? As I familiar with these output formats like HTML, XHTML and plain_text are information based resources(no need to compile). But Android supported for the .apk that is the format of applications running on Android OS. In Android application (typically a '.apk' ), it contains the zip format (encrypted) which is collection of jars, resources and manifest.xml etc... Why I said like that because when I developed an application for Android OS, I have to deal with a source code which contains java files, xml configuration files and resources etc... Then we have to compile it using android compiler. So I did a a experiment by tried to extract the apk file in Ubuntu. First I created a simple Android file with eclipse IDE and Android SDK. Then I export the code into '.apk' format[1]. I saw that it can be simulated on Android Emulator and work properly. But when .apk format extracted and try to see the file structure and contents in those files, extracted files aren't in the order as in Android source code. Also those have different type of file extensions and files are encrypted. My problem was, is it possible to run a apk which is not encrypted (as like XHTML-xsl , webhelp-xsl ) and create the structure by using XSLT ?. Or do we have to create the common structure according to the Android source code and compile is using Android tools and embedded the DocBook documentation into apk application. Thus we can open it in Android. Also we can use ANT to configure the procedure. What method should I do ? Is there any other successful way to do it ?. I also like to know, what should be the output of DocBook Android_xsl(a name that is made by me) should look like. I mean, what is final goal of this project look like. Further, I'd very much appreciate if you can provide me some directives and guide me. Thank you in Advance, Jirka !. [0]. http://docbook.xmlpress.net/tiki-index.php?page=Ideas2012#Extend_supported_output_formats [1]. http://www.androiddevelopment.org/tag/apk/ -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
Hi Jirka : I'm very much happy to see you as mentoring the project idea of Extended support output formats[0]. Also Thank you very much for volunteer as a mentor to this idea under DocBook. In this mail thread, I posted some of my ideas according to the understanding about project idea and suggestions on it. I think that you got those posts from DocBook-apps mailing list. So, what do you think about those solutions?. Your comments on those are highly appreciate. Also, I posted some questions on ambiguities which I have under this idea. If you can explain those, it will help me greatly. Further,can you give me some guidance and resources which would help me to get into goal ?. ( If you didn't receive previous mail in this thread, please be kind enough to inform me. Then I can prepare a summary on those posts and sent back to you ). Thank you in Advance !. [0]. http://docbook.xmlpress.net/tiki-index.php?page=Ideas2012 -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993 2012/3/21 gihan karunarathne gckarunarat...@gmail.com Hi David, Hi mentors : Thank you very much David again for your interesting towards this project idea and help me to get through this. Some are more worked up than others, but you're free to change based on your interests, feedback, community interest, and so on. I will track on the feedback and other helps which are really help me to get through the process. But I keep focus on learning XSLT and XSL with the hope of contribute to the DocBook projects. So, I followed some tutorials of vogella [1] [2]. Those are really help me to sharpen my understanding about technologies. Also I following some complete guide tutorials [3]. In the case of building an apk from DocBook, much of the source for the apk will be generated from DocBook at build time. I don't understand this point clearly. Can you explain it further, David? I would look around for some .apk books and see how close the html and other internal resources are to .epub. If a .apk book is very close to .epub, then it should be a pretty easy task to turn the .epub you currently get from DocBook into a .apk file. I don't know about the idea of .apk is going to implement from the scratch or in top of the DocBook. In case, it can implement like .epub built with the help of XHTML then it will be a easy task. I can build it by studying .apk from its basic [4]. Or try with some alternative method which will get the external dependencies support and get the job done. As an example, I found that AIR application for Android with the Flex SDK [5] is doing such kind of alternative. According to my understanding with my experience about Android by roughly go through this web page, they are simply creating a Android source and manifest.xml file to configure Android settings. It also ask for java class which is similar to Activity class in Android and use Android SDK to build .apk. According to my idea, we can generate those manifest.xml and other java class which help to build GUI in the Android by using XSLT transformation. Then use Android SDK to compile and build .apk by configure dependencies in Ant script. Other way, we can use from the beginning method to build .apk by using XSLT transformation. If I have misunderstanding or some wrong idea with regarding this, please correct me. Then If that's the case, you would want to find other stuff to add to the proposal so you have enough to do over the summer. I will seek for another output format during this period. We should also ask the other mentors if any are interested in this project and what their thoughts are. I'm hoping they'll chime in. Yes David. I also very appreciate if a mentor can help to me through out this project idea. We will wait until some one help us. I also think, this is a critical point with regarding where should I heading. If I tried to follow any difficult method to implement this idea, I'm wasting my time. So, any thoughts about this idea are highly valuable and appreciate for me. Thank you in Advance !. [1]. http://www.vogella.de/articles/DocBook/article.html#epub [2]. http://www.vogella.de/articles/XSLT/article.html [3]. http://www.w3.org/TR/xsl/ [4]. http://forum.sdx-developers.com/index.php?topic=3472.0 [5]. http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac25d3d8c712b2d86751e-8000.html
Re: [docbook-apps] Extend supported output formats
Hi Gihan, On Thu, 22 Mar 2012 03:20:35 +0530 gihan karunarathne gckarunarat...@gmail.com wrote: [...] But I keep focus on learning XSLT and XSL with the hope of contribute to the DocBook projects. So, I followed some tutorials of vogella [1] [2]. Those are really help me to sharpen my understanding about technologies. Also I following some complete guide tutorials [3]. In case you need further information about DocBook, XSLT, and customization, may I point you to my cookbook? It is freely available as HTML: http://doccookbook.sourceforge.net/html/en/DoCookBook.html Hope you find it useful. :) -- Gruß/Regards, Thomas Schraitle - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Extend supported output formats
Hi Thomas : Thank you very much for your interesting about my procedure under * Android-xsl* project idea. I have a quick look on the book. It seems to be written in user friendly manner and easy to understand. I hope, it will accelerate my learning process towards the DocBook. I like to invite other contributes and GSoC students to have a look on this book. Thank you !. On Thu, Mar 22, 2012 at 1:04 PM, Thomas Schraitle tom_s...@web.de wrote: Hi Gihan, On Thu, 22 Mar 2012 03:20:35 +0530 gihan karunarathne gckarunarat...@gmail.com wrote: [...] But I keep focus on learning XSLT and XSL with the hope of contribute to the DocBook projects. So, I followed some tutorials of vogella [1] [2]. Those are really help me to sharpen my understanding about technologies. Also I following some complete guide tutorials [3]. In case you need further information about DocBook, XSLT, and customization, may I point you to my cookbook? It is freely available as HTML: http://doccookbook.sourceforge.net/html/en/DoCookBook.html Hope you find it useful. :) -- Gruß/Regards, Thomas Schraitle - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
Hi Gihan, I happy to hear that my tutorials (vogella) were helpful. Good luck with your project. Best regards, Lars 2012/3/21 gihan karunarathne gckarunarat...@gmail.com Hi David, Hi mentors : Thank you very much David again for your interesting towards this project idea and help me to get through this. Some are more worked up than others, but you're free to change based on your interests, feedback, community interest, and so on. I will track on the feedback and other helps which are really help me to get through the process. But I keep focus on learning XSLT and XSL with the hope of contribute to the DocBook projects. So, I followed some tutorials of vogella [1] [2]. Those are really help me to sharpen my understanding about technologies. Also I following some complete guide tutorials [3]. In the case of building an apk from DocBook, much of the source for the apk will be generated from DocBook at build time. I don't understand this point clearly. Can you explain it further, David? I would look around for some .apk books and see how close the html and other internal resources are to .epub. If a .apk book is very close to .epub, then it should be a pretty easy task to turn the .epub you currently get from DocBook into a .apk file. I don't know about the idea of .apk is going to implement from the scratch or in top of the DocBook. In case, it can implement like .epub built with the help of XHTML then it will be a easy task. I can build it by studying .apk from its basic [4]. Or try with some alternative method which will get the external dependencies support and get the job done. As an example, I found that AIR application for Android with the Flex SDK [5] is doing such kind of alternative. According to my understanding with my experience about Android by roughly go through this web page, they are simply creating a Android source and manifest.xml file to configure Android settings. It also ask for java class which is similar to Activity class in Android and use Android SDK to build .apk. According to my idea, we can generate those manifest.xml and other java class which help to build GUI in the Android by using XSLT transformation. Then use Android SDK to compile and build .apk by configure dependencies in Ant script. Other way, we can use from the beginning method to build .apk by using XSLT transformation. If I have misunderstanding or some wrong idea with regarding this, please correct me. Then If that's the case, you would want to find other stuff to add to the proposal so you have enough to do over the summer. I will seek for another output format during this period. We should also ask the other mentors if any are interested in this project and what their thoughts are. I'm hoping they'll chime in. Yes David. I also very appreciate if a mentor can help to me through out this project idea. We will wait until some one help us. I also think, this is a critical point with regarding where should I heading. If I tried to follow any difficult method to implement this idea, I'm wasting my time. So, any thoughts about this idea are highly valuable and appreciate for me. Thank you in Advance !. [1]. http://www.vogella.de/articles/DocBook/article.html#epub [2]. http://www.vogella.de/articles/XSLT/article.html [3]. http://www.w3.org/TR/xsl/ [4]. http://forum.sdx-developers.com/index.php?topic=3472.0 [5]. http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac25d3d8c712b2d86751e-8000.html -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993 -- Lars http://www.vogella.de - Eclipse, Android and Java Tutorials http://www.twitter.com/vogella - Lars on Twitter
Re: [docbook-apps] Extend supported output formats
Hi Gihan, On Thu, 22 Mar 2012 14:15:05 +0530 gihan karunarathne gckarunarat...@gmail.com wrote: Thank you very much for your interesting about my procedure under * Android-xsl* project idea. I have a quick look on the book. It seems to be written in user friendly manner and easy to understand. I hope, it will accelerate my learning process towards the DocBook. I like to invite other contributes and GSoC students to have a look on this book. Thank you. Keep in mind, the book is a draft and work in progress, but I think it contains some useful topics. :) Good luck with your project. -- Gruß/Regards, Thomas Schraitle - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Extend supported output formats
Hi Lars Vogel : Thank you very much !. It's nice to meet you in DocBook. I got to know about basics of Android from a tutorial of you. Great work, keep it up !. On Thu, Mar 22, 2012 at 3:14 PM, Lars Vogel lars.vo...@googlemail.comwrote: Hi Gihan, I happy to hear that my tutorials (vogella) were helpful. Good luck with your project. Best regards, Lars 2012/3/21 gihan karunarathne gckarunarat...@gmail.com Hi David, Hi mentors : Thank you very much David again for your interesting towards this project idea and help me to get through this. Some are more worked up than others, but you're free to change based on your interests, feedback, community interest, and so on. I will track on the feedback and other helps which are really help me to get through the process. But I keep focus on learning XSLT and XSL with the hope of contribute to the DocBook projects. So, I followed some tutorials of vogella [1] [2]. Those are really help me to sharpen my understanding about technologies. Also I following some complete guide tutorials [3]. In the case of building an apk from DocBook, much of the source for the apk will be generated from DocBook at build time. I don't understand this point clearly. Can you explain it further, David? I would look around for some .apk books and see how close the html and other internal resources are to .epub. If a .apk book is very close to .epub, then it should be a pretty easy task to turn the .epub you currently get from DocBook into a .apk file. I don't know about the idea of .apk is going to implement from the scratch or in top of the DocBook. In case, it can implement like .epub built with the help of XHTML then it will be a easy task. I can build it by studying .apk from its basic [4]. Or try with some alternative method which will get the external dependencies support and get the job done. As an example, I found that AIR application for Android with the Flex SDK [5] is doing such kind of alternative. According to my understanding with my experience about Android by roughly go through this web page, they are simply creating a Android source and manifest.xml file to configure Android settings. It also ask for java class which is similar to Activity class in Android and use Android SDK to build .apk. According to my idea, we can generate those manifest.xml and other java class which help to build GUI in the Android by using XSLT transformation. Then use Android SDK to compile and build .apk by configure dependencies in Ant script. Other way, we can use from the beginning method to build .apk by using XSLT transformation. If I have misunderstanding or some wrong idea with regarding this, please correct me. Then If that's the case, you would want to find other stuff to add to the proposal so you have enough to do over the summer. I will seek for another output format during this period. We should also ask the other mentors if any are interested in this project and what their thoughts are. I'm hoping they'll chime in. Yes David. I also very appreciate if a mentor can help to me through out this project idea. We will wait until some one help us. I also think, this is a critical point with regarding where should I heading. If I tried to follow any difficult method to implement this idea, I'm wasting my time. So, any thoughts about this idea are highly valuable and appreciate for me. Thank you in Advance !. [1]. http://www.vogella.de/articles/DocBook/article.html#epub [2]. http://www.vogella.de/articles/XSLT/article.html [3]. http://www.w3.org/TR/xsl/ [4]. http://forum.sdx-developers.com/index.php?topic=3472.0 [5]. http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac25d3d8c712b2d86751e-8000.html -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993 -- Lars http://www.vogella.de - Eclipse, Android and Java Tutorials http://www.twitter.com/vogella - Lars on Twitter -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
Hi Richard, Hi David : I highly appreciate your support for my post. It was a mighty encouragement for me to motivate towards the project idea of Extend supported output formats. I also think, DocBook community is going to take a good step with expanding its content towards the Android and iPad etc which can be consider as convergence technologies. I read some about epub extension which is already as xsl sheets in DocBook. Also epub [0] is a zip format file type with a predefined content and it used XHTML for its conversion as like webhelp. Is it good method to follow the implementation of epub or webhelp to get an idea about this project idea ?. Are there any suggestions ?. I highly appreciate those guidance at this movement. David; I also saw that applicant/s can to choose at-least two output formats(preferred) to work on Google Summer of Code under this idea. But the idea page seems to be changed its content. I try to understand the idea with Android which I familiar more than others and enthusiastic. Then it will give me good foundation to move into one of another or may be more than one. Thank you very much David to address it here. I search for some resource to get some idea about Android file format '.apk'. As I understood, when I create a Android application, I have to maintain in my program's code such as assets, manifest, resources, packaged java classes etc... When I'm going to host my application, it should be distributed in the .apk format. To create a Android file, first the files in source are compiled, and then all of its parts are packaged into one file. So, APK means set zipped jar files [1]. Please, correct me if I'm heading to a wrong path. I'm think, it is better to understand the APK format and General Structure of an APK[2] will give me a good explanation on it. If some one can give documentation/articles explaining how can get into this project idea, it's highly appreciate. Thank you in Advance !. [0]. http://en.wikipedia.org/wiki/EPUB [1]. http://en.wikipedia.org/wiki/APK_%28file_format%29 [2]. http://forum.sdx-developers.com/index.php?topic=3472.0 -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Gihan, So you're free to submit whatever proposal you want for a GSoC project. The items on the ideas pages are just starting points that various people jotted down. Some are more worked up than others, but you're free to change based on your interests, feedback, community interest, and so on. In the case of building an apk from DocBook, much of the source for the apk will be generated from DocBook at build time. I would look around for some .apk books and see how close the html and other internal resources are to .epub. If a .apk book is very close to .epub, then it should be a pretty easy task to turn the .epub you currently get from DocBook into a .apk file. If that's the case, you would want to find other stuff to add to the proposal so you have enough to do over the summer. We should also ask the other mentors if any are interested in this project and what their thoughts are. I'm hoping they'll chime in. Thanks, David On 03/21/2012 08:34 AM, gihan karunarathne wrote: Hi Richard, Hi David : I highly appreciate your support for my post. It was a mighty encouragement for me to motivate towards the project idea of Extend supported output formats. I also think, DocBook community is going to take a good step with expanding its content towards the Android and iPad etc which can be consider as convergence technologies. I read some about epub extension which is already as xsl sheets in DocBook. Also epub [0] is a zip format file type with a predefined content and it used XHTML for its conversion as like webhelp. Is it good method to follow the implementation of epub or webhelp to get an idea about this project idea ?. Are there any suggestions ?. I highly appreciate those guidance at this movement. David; I also saw that applicant/s can to choose at-least two output formats(preferred) to work on Google Summer of Code under this idea. But the idea page seems to be changed its content. I try to understand the idea with Android which I familiar more than others and enthusiastic. Then it will give me good foundation to move into one of another or may be more than one. Thank you very much David to address it here. I search for some resource to get some idea about Android file format '.apk'. As I understood, when I create a Android application, I have to maintain in my program's code such as assets, manifest, resources, packaged java classes etc... When I'm going to host my application, it should be distributed in the .apk format. To create a Android file, first the files in source are compiled, and then all of its parts are packaged into one file. So, APK means set zipped jar files [1]. Please, correct me if I'm heading to a wrong path. I'm think, it is better to understand the APK format and General Structure of an APK[2] will give me a good explanation on it. If some one can give documentation/articles explaining how can get into this project idea, it's highly appreciate. Thank you in Advance !. [0]. http://en.wikipedia.org/wiki/EPUB [1]. http://en.wikipedia.org/wiki/APK_%28file_format%29 [2]. http://forum.sdx-developers.com/index.php?topic=3472.0 -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPaja9AAoJEMHeSXG7afUhJAsH/2uh60y55L6uW4Vts6ANZ271 0ggUZsLmyr1O6iPXO8yrepfz/lFusZFi9lNgZXEe5cM/ilFhFlVM9YoFKGrd+q9/ On/frvuRDtBCmX1d+LymTf6jXNfqhEbN/x3fojQd39J05j9FjfBozGDAtP6jPwLf Kt4OG4FE6SKmzHJwDMa/SpOTjgO6M5rQdTyCfG0BRHtFpTAPxiTn7HHZuHdhBT+2 fN4yqKRXq3K8s0IPiwkGWEOFDUisA+6OdFFJ3/d5pAw+E5ifHxUHxzqk7Nfh1j/d xIiySewpib5a78yMpkrn1/38kGdLw58AFpHy1/UXCrEltbfwFUYvOhAMcLl5xxI= =oA5U -END PGP SIGNATURE- - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Extend supported output formats
Hi David, Hi mentors : Thank you very much David again for your interesting towards this project idea and help me to get through this. Some are more worked up than others, but you're free to change based on your interests, feedback, community interest, and so on. I will track on the feedback and other helps which are really help me to get through the process. But I keep focus on learning XSLT and XSL with the hope of contribute to the DocBook projects. So, I followed some tutorials of vogella [1] [2]. Those are really help me to sharpen my understanding about technologies. Also I following some complete guide tutorials [3]. In the case of building an apk from DocBook, much of the source for the apk will be generated from DocBook at build time. I don't understand this point clearly. Can you explain it further, David? I would look around for some .apk books and see how close the html and other internal resources are to .epub. If a .apk book is very close to .epub, then it should be a pretty easy task to turn the .epub you currently get from DocBook into a .apk file. I don't know about the idea of .apk is going to implement from the scratch or in top of the DocBook. In case, it can implement like .epub built with the help of XHTML then it will be a easy task. I can build it by studying .apk from its basic [4]. Or try with some alternative method which will get the external dependencies support and get the job done. As an example, I found that AIR application for Android with the Flex SDK [5] is doing such kind of alternative. According to my understanding with my experience about Android by roughly go through this web page, they are simply creating a Android source and manifest.xml file to configure Android settings. It also ask for java class which is similar to Activity class in Android and use Android SDK to build .apk. According to my idea, we can generate those manifest.xml and other java class which help to build GUI in the Android by using XSLT transformation. Then use Android SDK to compile and build .apk by configure dependencies in Ant script. Other way, we can use from the beginning method to build .apk by using XSLT transformation. If I have misunderstanding or some wrong idea with regarding this, please correct me. Then If that's the case, you would want to find other stuff to add to the proposal so you have enough to do over the summer. I will seek for another output format during this period. We should also ask the other mentors if any are interested in this project and what their thoughts are. I'm hoping they'll chime in. Yes David. I also very appreciate if a mentor can help to me through out this project idea. We will wait until some one help us. I also think, this is a critical point with regarding where should I heading. If I tried to follow any difficult method to implement this idea, I'm wasting my time. So, any thoughts about this idea are highly valuable and appreciate for me. Thank you in Advance !. [1]. http://www.vogella.de/articles/DocBook/article.html#epub [2]. http://www.vogella.de/articles/XSLT/article.html [3]. http://www.w3.org/TR/xsl/ [4]. http://forum.sdx-developers.com/index.php?topic=3472.0 [5]. http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac25d3d8c712b2d86751e-8000.html -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
[docbook-apps] Extend supported output formats
Hi devs : I've gone through the idea page of DocBook and found the project idea Extend supported output formats [1] very interesting to me mainly because I have good background knowledge about Ant and Android. I'm doing an Android application as my level-3 software project and also I'm a fan of smart phones, specially about Android. After I started poking around DocBook, I understood that XSLT language processor[2] get an XML source document, and an XSLT stylesheet( typically the DocBook xsl sheets [3] ) and produces an output document according to the rules are provided in XSLT style sheet. If I misunderstood the procedure, please correct me ?. I installed XSLTProc[4] and download the DocBook xsl style sheets from sourceforge repository [5]. Then using DocBook ubuntu documentation [6], I create a test.html file by using test.xml file. It was successfully built. I used a command similar to this *xsltproc -o test.html /usr/share/xml/docbook/stylesheet/nwalsh/xhtml/docbook.xsl test.xml* According to my understanding, I used a external xslt processor to transform test.xml file to test.html according to the DocBook html style sheet. As I understood, the main goal of the project is generating an another type of formats file (ex:Android,iPad) by a XSLTProcessor. So, in order to do that we want xsl style sheet which includes instructions and other directives that guide the processor in the production of the output document, right? If so, I think it's better if I looked at how the current DocBook xsl style sheets can be use to implement those output formats. Further, I'd very much appreciate if you can provide me some directives and guide me. Specially, I'm looking for documentation/articles explaining how Ant and xsl is currently used in the system. Please tell me if I missed something important !. I also need to clarify the idea which is in the idea page[1]; *“Output format packages” output by the DocBook style sheets would be easily consumable / installable by hosting applications.* What does it mean by easily consumable / installable ?. Can you explain further ?. As I familiar with these output formats like HTML, PDF and plain_text are information based resources. But Android supported for the .apk format that the format of applications running on Android OS. So, what are the output formats which are going to produce by Android-xsl sheets and for others in the list ? Further, I welcome any advices that you'd like to give for a beginner DocBook developer interested in contributing. Thank you in Advance !. [1]. http://docbook.xmlpress.net/tiki-index.php?page=Ideas2012#Extend_supported_output_formats [2]. http://en.wikipedia.org/wiki/XSL_Transformations [3]. http://en.wikipedia.org/wiki/DocBook_XSL [4]. http://xmlsoft.org/xslt/xsltproc2.html [5]. http://sourceforge.net/projects/docbook/files/docbook-xsl/ [6]. https://help.ubuntu.com/community/DocBook -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
Gihan, Thanks for your interest in the DocBook project and the Google Summer of Code. It seems like you have made a good start. I suggest looking at DocBook XSL: The Complete Guide, by Bob Stayton, for the best single reference to the stylesheets. You can find an online version at http://sagehill.net. Currently, ant is not required to build or use the stylesheets. Regarding your question about the idea page, I will leave that for other's on this list to address. I suspect the person who wrote that particular idea is on the list. Best Regards, Dick Hamilton --- XML Press XML for Technical Communicators http://xmlpress.net hamil...@xmlpress.net On Mar 19, 2012, at 2:01 PM, gihan karunarathne wrote: Hi devs : I've gone through the idea page of DocBook and found the project idea Extend supported output formats [1] very interesting to me mainly because I have good background knowledge about Ant and Android. I'm doing an Android application as my level-3 software project and also I'm a fan of smart phones, specially about Android. After I started poking around DocBook, I understood that XSLT language processor[2] get an XML source document, and an XSLT stylesheet( typically the DocBook xsl sheets [3] ) and produces an output document according to the rules are provided in XSLT style sheet. If I misunderstood the procedure, please correct me ?. I installed XSLTProc[4] and download the DocBook xsl style sheets from sourceforge repository [5]. Then using DocBook ubuntu documentation [6], I create a test.html file by using test.xml file. It was successfully built. I used a command similar to this xsltproc -o test.html /usr/share/xml/docbook/stylesheet/nwalsh/xhtml/docbook.xsl test.xml According to my understanding, I used a external xslt processor to transform test.xml file to test.html according to the DocBook html style sheet. As I understood, the main goal of the project is generating an another type of formats file (ex:Android,iPad) by a XSLTProcessor. So, in order to do that we want xsl style sheet which includes instructions and other directives that guide the processor in the production of the output document, right? If so, I think it's better if I looked at how the current DocBook xsl style sheets can be use to implement those output formats. Further, I'd very much appreciate if you can provide me some directives and guide me. Specially, I'm looking for documentation/articles explaining how Ant and xsl is currently used in the system. Please tell me if I missed something important !. I also need to clarify the idea which is in the idea page[1]; “Output format packages” output by the DocBook style sheets would be easily consumable / installable by hosting applications. What does it mean by easily consumable / installable ?. Can you explain further ?. As I familiar with these output formats like HTML, PDF and plain_text are information based resources. But Android supported for the .apk format that the format of applications running on Android OS. So, what are the output formats which are going to produce by Android-xsl sheets and for others in the list ? Further, I welcome any advices that you'd like to give for a beginner DocBook developer interested in contributing. Thank you in Advance !. [1]. http://docbook.xmlpress.net/tiki-index.php?page=Ideas2012#Extend_supported_output_formats [2]. http://en.wikipedia.org/wiki/XSL_Transformations [3]. http://en.wikipedia.org/wiki/DocBook_XSL [4]. http://xmlsoft.org/xslt/xsltproc2.html [5]. http://sourceforge.net/projects/docbook/files/docbook-xsl/ [6]. https://help.ubuntu.com/community/DocBook -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993 - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Extend supported output formats
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Gihan, I didn't add that entry to the ideas page, but of them, the most interesting to me is creating content for Android. In particular, I enjoy reading books in the .apk format [1] on my Nexus S over .epub. I suspect .apk and .epub are similar formats and .epub xsls already exist so they could be modified to produce .apk. I don't know if .apk as an output format is enough to keep you busy for a whole summer. If not, you could throw in some other work. I know O'Reilly books are often available in epub and apk formats. Regards, David [1] https://en.wikipedia.org/wiki/APK_%28file_format%29 On 03/19/2012 04:11 PM, Richard Hamilton wrote: Gihan, Thanks for your interest in the DocBook project and the Google Summer of Code. It seems like you have made a good start. I suggest looking at DocBook XSL: The Complete Guide, by Bob Stayton, for the best single reference to the stylesheets. You can find an online version at http://sagehill.net. Currently, ant is not required to build or use the stylesheets. Regarding your question about the idea page, I will leave that for other's on this list to address. I suspect the person who wrote that particular idea is on the list. Best Regards, Dick Hamilton --- XML Press XML for Technical Communicators http://xmlpress.net hamil...@xmlpress.net On Mar 19, 2012, at 2:01 PM, gihan karunarathne wrote: Hi devs : I've gone through the idea page of DocBook and found the project idea Extend supported output formats [1] very interesting to me mainly because I have good background knowledge about Ant and Android. I'm doing an Android application as my level-3 software project and also I'm a fan of smart phones, specially about Android. After I started poking around DocBook, I understood that XSLT language processor[2] get an XML source document, and an XSLT stylesheet( typically the DocBook xsl sheets [3] ) and produces an output document according to the rules are provided in XSLT style sheet. If I misunderstood the procedure, please correct me ?. I installed XSLTProc[4] and download the DocBook xsl style sheets from sourceforge repository [5]. Then using DocBook ubuntu documentation [6], I create a test.html file by using test.xml file. It was successfully built. I used a command similar to this xsltproc -o test.html /usr/share/xml/docbook/stylesheet/nwalsh/xhtml/docbook.xsl test.xml According to my understanding, I used a external xslt processor to transform test.xml file to test.html according to the DocBook html style sheet. As I understood, the main goal of the project is generating an another type of formats file (ex:Android,iPad) by a XSLTProcessor. So, in order to do that we want xsl style sheet which includes instructions and other directives that guide the processor in the production of the output document, right? If so, I think it's better if I looked at how the current DocBook xsl style sheets can be use to implement those output formats. Further, I'd very much appreciate if you can provide me some directives and guide me. Specially, I'm looking for documentation/articles explaining how Ant and xsl is currently used in the system. Please tell me if I missed something important !. I also need to clarify the idea which is in the idea page[1]; “Output format packages” output by the DocBook style sheets would be easily consumable / installable by hosting applications. What does it mean by easily consumable / installable ?. Can you explain further ?. As I familiar with these output formats like HTML, PDF and plain_text are information based resources. But Android supported for the .apk format that the format of applications running on Android OS. So, what are the output formats which are going to produce by Android-xsl sheets and for others in the list ? Further, I welcome any advices that you'd like to give for a beginner DocBook developer interested in contributing. Thank you in Advance !. [1]. http://docbook.xmlpress.net/tiki-index.php?page=Ideas2012#Extend_supported_output_formats [2]. http://en.wikipedia.org/wiki/XSL_Transformations [3]. http://en.wikipedia.org/wiki/DocBook_XSL [4]. http://xmlsoft.org/xslt/xsltproc2.html [5]. http://sourceforge.net/projects/docbook/files/docbook-xsl/ [6]. https://help.ubuntu.com/community/DocBook -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993 - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla -
