Free 4.05 m33 software for linux

Pod::HTML2Pod Perl module can translate HTML into POD.

SYNOPSIS

# Use the program html2pod that comes in this dist, or:
use Pod::HTML2Pod;
print Pod::HTML2Pod::convert(
file => my_stuff.html, # input file
a_href => 1, # try converting links
);

Larry Wall once said (1999-08-27, on the pod-people list, I do believe): "The whole point of pod is to get people to document stuff they wouldnt document in any other form."

To that end, I wrote this module so that people who are unpracticed with POD but in a hurry to simply document their programs or modules, could write their documentation in simple HTML, and convert that to POD. Thats what this module does.

Specifically, this module bends over backwards to try to turn even vaguely plausable HTML into POD -- and when in doubt, it simply ignores things that it doesnt know about, or cant render.

FUNCTIONS

This module provides one documented function, which it does not export:
Pod::HTML2Pod::convert( ...options... )

This returns a single scalar value containing the converted POD text, with some comments after the end.

This function takes options:

file => FILENAME,

Specifies that the HTML code is to be read from the filename given.

handle => *HANDLE,

Specifies that the HTML code is to be read from the open filehandle given (e.g., $fh_obj, *HANDLE, *HANDLE{IO}, etc.) If you specify this, but fail to specify an actual handle object, inscrutible errors may result.

content => STRING,

Specifies that the HTML code is in the string given. (Alternately, pass a reference to the scalar: content => $stuff.)

tree => OBJ,

Specifies that the HTML document is contained in the given HTML::TreeBuilder object (or HTML::Element object, at least).

a_name => BOOLEAN,

Specifies whether you want to try converting < a name="..." > elements. By default this is off -- i.e., such elements are ignored.

a_href => BOOLEAN,

Specifies whether you want to try converting < a href="..." > elements. By default this is off -- i.e., such elements are ignored. If on, bear in mind that relative URLs cannot be properly converted to POD -- any relative URLs will be complained about in comments after the end of the document. Normal absolute URLs will be treated as best they can be. Note that URLs beginning "pod:..." will be turned into POD links to whatever follows; that is, "pod:Getopt::Std" is turned into L< Getopt::Std >

debug => INTEGER,

Puts Pod::HTML2Pod into verbose debug mode for the duration of processing this this HTML document. INTEGER can be 0 for no debug output, 1 for a moderate amount that will cause the HTML syntax tree to be be dumped at the start of the conversion, and 2 for that plus a dump of the intermediate POD doctree, plus a few more inscrutible diagnostic messages. Looking at the trees dumped might be helpful in making sense of error messages that refer to a particular node in the parse tree.

VFU is console (text mode) file manager for UNIX/Linux.

During the years I tried to make short attractive list of features which VFU has. Attractive as Advertising above :) and it does not seem to work... at least it didnt for me and I never liked it.

I made all possible to make VFU cover all file managing needs and offer large set of behaviour options. If I succeeded or not, you can decide for yourself but without trying I believe noone can say for sure.

Installation:

1. how to compile vfu

run `make from vfu base directory

this should compile everything

to compile each part of vfu manually do this:

-- go to `vslib directory
-- run `make
-- go to `vfu directory
-- run `make

if something goes wrong, check these:

-- if your `curses.h file locations is not `/usr/include/ncurses
you have to change this in the Makefile.

-- if vslib library is not in the `../vslib directory you also
have to change this in the Makefile.

2. how to install vfu

run `install script from vfu base directory

install script checks if all required files are available/built and then does this:

cp vfu/vfu rx/rx_* /usr/local/bin
cp vfu.1 /usr/local/man/man1
cp vfu.conf /usr/local/etc

3. how to install vfu manually

-- you have to copy `vfu in the `/usr/local/bin or
`/usr/bin directory and set mode to 755 `rwxr-xr-x
the owner is not significant ( root is also possible ).

-- there is preliminary man page ( vfu.1 ) which could be
copied to /usr/man/man1.

-- copy all `rx/rx_* tools to /usr/local/bin
-- install Net::FTP perl module if needed.
(this is used for FTP support)

WARNING: make sure to remove all old personal cache files!

chaplin is a dvd chapter tool for Linux (and all other *ixes with libdvdread support).
The tool parses a DVD disc or image and extracts the exact duration for each chapter of a given title. Then the total list of chapters is split into a user-selectable number of subsets. Each subset should have approximately the same duration.
This is a very useful approach for multi-cd rips. You no longer simply split the movie in the middle of the frame count but you choose two sets of chapters for both parts which both have (almost) the same length. Then the disc-break is not at a rather random point (concering the story telling of the movie) but at the end of a dvd-chapter.
The chapter timings and the split sets are also very useful for chapter navigation (even on a single disc). The normal output mode of chaplin thus prints the chapters relative beginning time and the duration in a wide number of formats, ranging from seconds, frame counts to timestamps.
For S/VCD mastering chaplin can also produce vcdimager XML files for each disc. There a complete sequence structure with chapter entry points is defined. Also the full navigation setup for chapter hopping is provided. Additionally you can add chapter menus and automatically create the necessary menu pages out of thumbnails extracted directly from the DVD.
Installation:
You will need the libdvdread library for this tool. Specify its installation path in the provided Makefile. Then a simple call to "make" should build the chaplin binary. Copy the binary into your PATH. It is very useful to have transcode and vcdimager installed. The chaplin-genmenu tool needs transcode, ImageMagick and the mjpegtools.
Usage
Simple Usage
Just call chaplin the following way:
chaplin -d < dvd_path > -t < title >
This will display a chapter summary and places all chapters into a single subset (the default). This is useful for a single cd transfer. For multi-cd targets you specify the number of subsets with the -p option:
chaplin -d < dvd_path > -t < title > -p 2
This will divide the chapters up into 2 subsets. They should have almost the same size (this depends largely on the granularity of the provided chapters). Now you know which chapters fit on the first disc, know the exact frame count and you can calculate the exact bitrate for this part and finally transcode each part.
Chapter Info
Detailed info on the chapters is also available. Just add the -c option and per chapter info is printed:
chaplin ... -c
The standard output mode prints the relative offset of each chapter in the part. With the -l option you can replace this display with the length of each chapter.
S/VCD Mastering
If your target is a set of S/VCDs then the -x option is very useful:
chaplin ... -x MYMOVIE
MYMOVIE is the basename of the VCDs.
This option generates a XML S/VCD description for vcdimager which contains the exact chapter setup found by chaplin. The XML files are called "vcdNN.xml" and are created in the current directory. Name the MPEG files made from each subset "partNN.mpg" and place them in the same directory (NN=part number). Now a call to:
vcdxbuild vcdNN.xml
should generate a SVCD image with chapters and navigation information.
You can control the XML generation by passing suboptions to -x:
chaplin ... -x MYMOVIE,vcd,my%02d.xml,movie%02.mpg
This will generate VCD 2.0 XML files called myNN.xml and refers to MPEG movie files called movieNN.mpg. Do not forget to include a "%d" expression in the XML and MPEG file patterns. This will be replaced by the current part number. Numbering starts with one by default. Chaplin will begin with zero if you pass the -z option.
The second argument defines the type of the disc: vcd or svcd.
S/VCD Chapter Menus
Since version 1.9 chaplin also supports the creation of XML mastering files for S/VCDs with chapter menus. Add the -m option to -x to enable menu creation. You have to specify how many chapters are selectable on each menu page. chaplin will then create a menu page set for each of the selected parts and each menu page will contain at most the given number of entries:
chaplin ... -x MYMOVIE,svcd,my%02d.xml,movie%02.mpg,menu%02d-%d.mpg -m 6
In this example menu pages with up to six entries are created and labeled menu%02d-%d.mpg. Note the two %d replacement tags in the menu file name. The first one is replaced with the current part number and the second one counts the menu pages for this part. The generated XML will create a SVCD that shows the first menu page and allows to select the first six chapters with the numeric buttons. Furthermore you can switch to the next menu page.
The referenced menu pages are MPEG files containing still images. Each menu page should depict the chapters that can be selected on this page. The menu pages can be rendered automatically with the chaplin-genmenu tool.
Automatic Chapter Menu Generation
The chaplin-genmenu script creates the chapter menu still image MPG files that are referenced in the S/VCD chapter menus. To guide this tool what should be rendered on each menu page, you have to create a chapling menu description with the -g command:
chaplin ... -x ... -m < n > -g menu.txt
Now have a look a the created menu description text file. Its splitted into blocks for each menu page:
chaplin-menu 9
dvd "/dev/dvd" title 10 PAL 4:3
menu01-1.mpg 9 Part 1 Menu 1
01 0 Chapter 1
02 0 Chapter 2
03 0 Chapter 3
04 0 Chapter 4
05 0 Chapter 5
06 0 Chapter 6
07 0 Chapter 7
08 0 Chapter 8
09 0 Chapter 9
menu01-2.mpg 6 Part 1 Menu 2
10 0 Chapter 10
11 0 Chapter 11
12 0 Chapter 12
13 0 Chapter 13
14 0 Chapter 14
15 0 Chapter 15
The description contains the menu files to create and the chapters that are referenced on each page. You can edit this file to change the sample frame for each chapter that will be extracted to get the thumbnail image on the menu page: change the 0 value in the second column to the requested frame number. Finally you can edit the text that gets rendered on the menu pages: The title of each menu page is given in the title line (e.g.: "Part 1 Menu 1") and the chapter description after each frame number (e.g.: "Chapter 1").
Now run the menu page creator:
chaplin-genmenu menu.txt
This sets the dvd input device and title similar to the chaplin call and pass the generated chaplin menu description. This will create the MPG still images needed for S/VCD creation out of the XML file.
Specify -n NTSC if creating a NTSC and not a PAL S/VCD. Use -v if creating a VCD and not a SVCD.
With -o you can set a global offset for each chapter sample frame number. The -u option cleans up all temporary files created during program call. -x will display all external command calls to debug the tool.
With -b, -l and -f you can adjust the rendering of the menu pages.
Note that chaplin-genmenu is an incremental tool that only creates files that are not yet existing in the current path. So you can first call the tool (without -u) to create all intermediate files. Then you can retouch or repaint the menu PNG files and call the tool again to build MPG files. If you pass the -c switch then all files are recreated always.
Enhancements:
- fixed crash in some parts calculations
- output some video attributes in verbose mode
- new menu.txt format now passes all important parameters
- (dvd device, title, tvnorm and aspect ratio) automatically
- chaplin-genmenu:
- improved menu layout creation (hinted by S. Stordal)
- manual layout setup with -m option
- now reads all important parameters from chaplin directly
- thumbs now have correct aspect ratio
- default frame offset is now 16 (to skip partial gops)
- new switch -c allows to always recreate files
- new switch -s sets the font size
- renamed switches to be more consistent