[16:37] pmatulis_: next meeting is July 7th. :) I would change the topic but I don't have access === pmatulis_ is now known as pmatulis === dpm_ is now known as dpm [18:21] ahoneybun: did you get my last msg concerning markdown about a week ago? [18:22] repeat: [18:22] ahoneybun: concerning using Markdown, ideally GFM (Github Flavored Markdown), for the installation-guide. we need to know if our processes will accept it or not [18:22] ahoneybun: can you look into this? [18:23] processes? [18:23] I did not get that msg [18:23] ahoneybun: have you had the chance to look over how we publish stuff on help.ubuntu.com? [18:24] I have not tbh [18:26] ahoneybun: well your idea won't go very far then. specifically, we need to know if LP can handle markdown for managing translations, and if it does, what flavour of markdown [18:27] ahoneybun: i suggest you speak with someone knowledgeable in LP doc translations and explain your idea. there is a translations team, mailing list, etc [18:27] I don't even know how LP does it, I can never find the .po/.pot files [18:27] I was trying to prototype working with translations last night/this morning [18:28] ahoneybun: that's fine, but we also need to know if LP can handle it [18:29] ahoneybun: the translations aspect always thwarted me in the past when i thought of moving away from XML, maybe you will prove successful. it might be trivially easy, but it may not be [18:30] pmatulis: I have the Kubuntu Manual all moved to reST and uploaded to LP so we could prototype it [18:31] I have talked with someone over in the Kubuntu camp about using a translation tool called Pootle [18:32] ahoneybun: crux of the matter IMO is: LP can generate the POT file from the master english XML file. hence: can LP do the same from a master Markdown file [18:33] that is the question [18:33] yep [18:33] I'm learning how LP works with translations as we talk so I'm just catching up lol [18:36] as long as you remember that english is the root of the docs it becomes clearer - english XML -> POT file -> LP handles online translations of strings in POT file -> download PO file (result of translations) for every language -> generate HTML from each PO file [18:37] so the po file holds all the translations? [18:37] for each language, yes. so there are multiple PO files [18:37] I see [18:39] so for the current idea: english reST -> POT file -> Hope LP handles the translations in POT -> download the PO file -> Sphinx makes html for each PO file [18:39] from looking at this: http://sphinx-doc.org/intl.html?highlight=translations [18:40] sphinx can make POT files so we push them into LP and let it make PO files [18:40] rather then Pootle [18:41] ahoneybun: you may want to use sphinx for local tests or POC but ultimately the makefile we use needs to contain the instructions and currently we don't use sphinx. as long as we get updated PO files we should be good. concentrate on the main question above (see 'crux:') [18:42] and i would prefer GFM flavour of markdown [18:42] and recall that we are testing the installation-guide first [18:43] but we don't use github [18:44] ahoneybun: it may still be compatible, it is worth asking [18:45] I have not messed with using Markdown (in any form) with Sphinx tbh [18:47] well I just made some .po files with Sphinx [18:48] sorry pot [18:50] pmatulis: http://pastebin.ubuntu.com/11775051/ [18:50] where is the installation guide? [18:52] https://launchpad.net/installation-guide [18:52] https://help.ubuntu.com/lts/installation-guide/index.html [18:54] bzr branch lp:~ubuntu-core-dev/installation-guide/ubuntu ? [18:57] looks good to me [18:57] ahoneybun: Looks like that depends on what Markdown parser you use. [18:57] I'm in the sphinx-doc irc [18:59] should be asking LP people IMO about what capabilities LP has