Ralph Shumaker wrote: > James G. Sack (jim) wrote: >> Ralph Shumaker wrote: >>> Ralph Shumaker wrote: >>>> Menachem Shapiro wrote: >>>>> You could try setting up totem-xine, totem with an xine backend, >>>>> instead of gstreamer: >>>>> http://www.diffingo.com/blog/content/view/37/33/ >>>>> >>>>> If you are just looking for the gstreamer codecs to install, this >>>>> should be of interest: >>>>> http://www.gnome.org/projects/totem/#codecs >>>>> >>>>> Totem does support DVDs, but you need to install libdvdcss >>>>> >>>>> Menachem >>>> When I said "learning curve" above, I meant regarding multimedia >>>> stuff. I figured that it might just, oh, ... I don't know ..., work? >>>> >>>> Regarding the libdvdcss, I remember poking around a bit and I yum >>>> installed something that contained it, but it didn't seem to help. >>>> >>>> Multimedia is it's own learning curve and I've barely scratched the >>>> surface. >>>> >>>> But thanks for the hints. >>>> >>>> # yum list all | grep totem >>>> totem.i386 2.18.1-3.fc7 installed >>>> totem-mozplugin.i386 2.18.1-3.fc7 installed >>>> totem-plparser.i386 2.18.1-3.fc7 installed >>>> gnome-python2-totem.i386 2.18.0-1.fc7 fedora >>>> totem-devel.i386 2.18.1-3.fc7 fedora >>>> >>>> This doesn't reveal a totem-xine. >>>> >>>> # yum list all | grep xine >>>> gxine.i386 0.5.11-4.fc7 installed >>>> gxine-mozplugin.i386 0.5.11-4.fc7 installed >>>> oxine.i386 0.6.6-3.fc7 installed >>>> xine-lib.i386 1.1.7-1.fc7 installed >>>> xine-lib-devel.i386 1.1.7-1.fc7 installed >>>> xine-lib-extras.i386 1.1.7-1.fc7 installed >>>> xine-plugin.i386 1.0-3.fc7 installed >>>> xinetd.i386 2:2.3.14-12.fc7 installed >>>> >>>> This reflects the fact that I yum-installed everything xine. This >>>> didn't help. >>> Everything *fedora* xine, that is. >>> >>>> I'll take a look at the links you provided. >>> New repositories sure do expand horizons. >>> >>> Watching DVDs on my PC. This is kool. >>> >>> -me finally feels da need for da bigga screen now man >> >> Congratulations. >> >> But hey! .. you should write up a case study and recipe (in as much >> detail as you feel like) on your problem and overcoming it, and post it >> on the KPLUG Wiki. > > I don't have any experience writing documentation. But I guess I gotta > start somewhere, no? > > I've seen the KPLUG Wiki from a browsing standpoint, but don't know > anything about contributing. How do I go about it? Do I create content > in a text editor, word processor, or html editor? How do I upload it > once I'm done? I understand that a wiki is something that one person > can create and others can come and edit. I just don't know any of the > mechanisms.
There's more than one way... You can start just by writing in narrative style in a text editor. Don't worry about formatting except for blank lines between paragraphs. In fact, doing nothing beyond that would be sufficient for a lot of pages that might be posted on the wiki. Ours or anyones. If you find yourself liking section headers and various lists or tables or want to insert images, then there are relatively simple ways to do that, too. But I would have no reluctance recommending a pure-text paragraph only format to start. After you see how it looks rendered in a browser, you (we) can talk about possible questions you may have about presentation. If you're willing, maybe you can even critique the primitive help that already exists. On the main kernel panic site, clicking on the "Wiki" tab takes you to http://www.kernel-panic.org/wiki/FrontPage Not too far from the top is an invitation to click on the "WikiIntro" link to read some preliminary stuff, then eventually (on that page) you should probably click on the "WikiBasics" link. Bottom line is that you can and should "join" the KPLUG site, and then you can create trial documents in your own private (member) folder. After becoming a member, you can login and find a link called "my folder" which takes you to your private playpen. Look for the "add to folder" button and also the green "edit" tab -- things that show up when you are logged-in. You can simply explore the user interface, and upload files, create wiki pages (and cut-n-paste stuff in, say). If you want you can certainly experiment with html or "reStructured/Structured Text". But whichever "type of document" you choose, you can nevertheless try adding pure text at first, to see what it looks like. I would say that if you don't want a career in web page, it's not really useful to spend a whole lot of time on appearance. If you or anyone comes up with something that might profit from some kind of appearance polish, just ask for further help -- or play some more. Remember wiki stuff is easy to remove or even restore to prior versions, so don't be shy! :-) After you get beyond the first steps, we might (say) move the page into the public section for the whole world to profit from! Oh, and by-the-way, anyone (any member) can edit most of the pages in the public part of the Wiki. Typos and grammar-fixing is a no brainer. Adding additional information that extends the purpose of the page is also strongly encouraged. Major rewrites or arguments are generally considered unfriendly -- at least without first asking permission. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
