Commit b91a2582 authored by Tiago Bortoletto Vaz's avatar Tiago Bortoletto Vaz

adding files I think were not included during svn-upgrade

parent 924cca88
Gnome Subtitles
=============================
http://gnome-subtitles.sf.net
Authors
=======
Pedro Castro <dev pedrocastro.org> - Author and Maintainer
Artwork
=======
Stefan A. Keel (Sak) <http://sak.102010.org> - Logo and Icons
Documentation
=============
Erin Bloom <sciribe one.net> - User Manual
Translation
===========
Djihed Afifi (ar)
Joan Duran (ca)
Kamil Paral, Lucas Lommer, Petr Kovar, Rinu (cs)
Joe Hansen, Kristian Kjærgaard (da)
Felix Braun, Mario Blättermann (de)
Yumkee Lhamo (dz)
Nikolaos Agianniotis (el)
Philip Withnall (en_GB)
Gabriel Ruiz, Jorge González, Paulino Padial (es)
Ilkka Tuohela (fi)
Alexandre Imache, Claude Paroz, Frederic Peters, Stéphane Raimbault (fr)
Yair Hershkovitz (he)
Luca Ferretti, Simone Oberti (it)
Kjartan Maraas (nb)
Yannig Marchegay (oc)
Piotr Drąg, Tomasz Sałaciński (pl)
António Lima (pt)
César Veiga, Fábio Nogueira, Henrique P Machado, Leonardo Ferreira Fontenelle, Raphael Higino (pt_BR)
Nickolay V. Shmyrev (ru)
Daniel Nylander (sv)
Contributors
============
Cristina Yenyxe (Past Maintainer)
Fernando Zorrilla
Miguel Filho
Nazar Kulyk
Supporters
==========
Allan Vidal
David Prieto
Henrique Malheiro
Includes code from
==================
Fuse Media Centre (http://sf.net/projects/fusemc)
NCharDet (http://www.conceptdevelopment.net/Localization/NCharDet)
This diff is collapsed.
This diff is collapsed.
Installation Instructions
*************************
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that the
`configure' script does not know about. Run `./configure --help' for
details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
Installation Names
==================
By default, `make install' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', etc. You
can specify an installation prefix other than `/usr/local' by giving
`configure' the option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS KERNEL-OS
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the option `--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share, you
can create a site shell script called `config.site' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script). Here is a another example:
/bin/bash ./configure CONFIG_SHELL=/bin/bash
Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
configuration-related scripts to be executed by `/bin/bash'.
`configure' Invocation
======================
`configure' recognizes the following options to control how it operates.
`--help'
`-h'
Print a summary of the options to `configure', and exit.
`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
SUBDIRS = src data po help
ACLOCAL_AMFLAGS = -I m4
gstpbdir = $(pkglibdir)
gstpb_SCRIPTS = build/libgstreamer_playbin.so
$(gstpb_SCRIPTS):
cp -f src/libgstreamer_playbin.so build
dist-hook:
@if test -d "$(srcdir)/.git"; \
then \
echo Creating ChangeLog && \
( cd "$(top_srcdir)" && \
echo '# Generated by Makefile. Do not edit.'; echo; \
$(top_srcdir)/missing --run git log --stat ) > ChangeLog.tmp \
&& mv -f ChangeLog.tmp $(top_distdir)/ChangeLog \
|| ( rm -f ChangeLog.tmp ; \
echo Failed to generate ChangeLog >&2 ); \
else \
echo A git clone is required to generate a ChangeLog >&2; \
fi
EXTRA_DIST = \
autogen.sh \
gnome-doc-utils.make \
gnome-subtitles.mdp \
gnome-subtitles.mds \
intltool-extract.in \
intltool-merge.in \
intltool-update.in
DISTCLEANFILES = \
intltool-extract \
intltool-merge \
intltool-update \
gnome-doc-utils.make
This diff is collapsed.
This diff is collapsed.
Gnome Subtitles
=============================
http://gnome-subtitles.sf.net
Gnome Subtitles is a subtitle editor for the GNOME desktop. It supports the most
common text-based subtitle formats and allows for subtitle editing, translation
and synchronization.
Dependencies
============
Mono >= 1.1 (mono to run, gmcs to build)
Gtk+ >= 2.12
Gtk-Sharp >= 2.12
Glade-Sharp >= 2.12
GConf-Sharp >= 2.12
GStreamer >= 0.10
GStreamer-Plugins-Base >= 0.10
GtkSpell >= 2.0
Enchant >= 1.3
Building from Source
====================
Build it with the usual `./configure' followed by `make' commands.
Install it with `make install'.
Run it with `gnome-subtitles' or use the icon in the GNOME menu.
To try the program without installing it, `cd' to the `build' dir after building
it and run it with `mono gnome-subtitles.exe'.
The INSTALL file contains detailed information on this subject.
Building from Git
=================
Get the latest code from the GNOME Git repository:
git clone git://git.gnome.org/gnome-subtitles
Run `./autogen.sh' to generate the build scripts. Some packages are required:
autoconf
automake
glib-gettext
gnome-common
gnome-doc-utils
gtk-doc
intltool
libtool
pkg-config
You can now proceed to "Building from Source" to build Gnome Subtitles.
See http://live.gnome.org/Git/Developers for more information on how to use the
GNOME Git repository.
This diff is collapsed.
#!/bin/sh
# Run this to generate all the initial makefiles, etc.
srcdir=`dirname $0`
test -z "$srcdir" && srcdir=.
PKG_NAME="gnome-subtitles"
(test -f $srcdir/configure.ac \
&& test -f $srcdir/README \
&& test -d $srcdir/src/GnomeSubtitles) || {
echo -n "**Error**: Directory "\`$srcdir\'" does not look like the"
echo " top-level $PKG_NAME directory"
exit 1
}
which gnome-autogen.sh || {
echo "You need to install gnome-common from GNOME SVN and make"
echo "sure the gnome-autogen.sh script is in your \$PATH."
exit 1
}
REQUIRED_AUTOMAKE_VERSION=1.9
REQUIRED_INTLTOOL_VERSION=0.35
USE_GNOME2_MACROS=1
. gnome-autogen.sh
<configuration>
<dllmap dll="libenchant" target="libenchant.so.1" />
<dllmap dll="libgtkspell" target="libgtkspell.so.0" />
</configuration>
This diff is collapsed.
AC_PREREQ(2.58)
AC_INIT(gnome-subtitles, 0.9.1, http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-subtitles)
GNOME_COMMON_INIT
GNOME_DOC_INIT
GTK_DOC_CHECK([1.0])
AC_CONFIG_MACRO_DIR([m4])
AC_CONFIG_SRCDIR([configure.ac])
AM_INIT_AUTOMAKE([1.9 tar-ustar])
AM_MAINTAINER_MODE
IT_PROG_INTLTOOL([0.35.0])
AC_PROG_INSTALL
AC_PREFIX_PROGRAM(mono)
dnl Gettext stuff.
GETTEXT_PACKAGE=gnome-subtitles
AC_SUBST(GETTEXT_PACKAGE)
AC_DEFINE_UNQUOTED(GETTEXT_PACKAGE,"$GETTEXT_PACKAGE", [Gettext package])
AM_GLIB_GNU_GETTEXT
dnl pkg-config
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
if test "x$PKG_CONFIG" = "xno"; then
AC_MSG_ERROR([You need to install pkg-config])
fi
dnl C# compiler
AC_PATH_PROG(CSC, csc, no)
AC_PATH_PROG(MCS, gmcs, no)
AC_PATH_PROG(MONO, mono, no)
CS="C#"
if test "x$CSC" = "xno" -a "x$MCS" = "xno" ; then
dnl AC_MSG_ERROR([You need to install a C# compiler])
AC_MSG_ERROR([No $CS compiler found])
fi
if test "x$MCS" = "xno" ; then
MCS=$CSC
fi
if test "x$MONO" = "xno"; then
AC_MSG_ERROR([No mono runtime found])
fi
dnl create build dir if it does not exist
if test ! -d "build"
then
mkdir build
fi
dnl pkg-config
MONO_REQUIRED_VERSION=1.1
GTKSHARP_REQUIRED_VERSION=2.12
GTK_REQUIRED_VERSION=2.12
PKG_CHECK_MODULES(gstreamer, [gstreamer-0.10 >= 0.10])
PKG_CHECK_MODULES(gstreamer_plugins_base, [gstreamer-plugins-base-0.10 >= 0.10])
AC_SUBST(gstreamer_CFLAGS)
AC_SUBST(gstreamer_LIBS)
PKG_CHECK_MODULES(MONO, mono >= $MONO_REQUIRED_VERSION)
PKG_CHECK_MODULES(GTKSHARP, gtk-sharp-2.0 glade-sharp-2.0 gconf-sharp-2.0 >= $GTKSHARP_REQUIRED_VERSION)
PKG_CHECK_MODULES(GTK, gtk+-2.0 >= $GTK_REQUIRED_VERSION)
dnl Check gtk-sharp version
PKG_CHECK_MODULES(GTKSHARP_INVALID, gtk-sharp-2.0 >= 2.12.2 gtk-sharp-2.0 <= 2.12.6, gtksharp_invalid=true, gtksharp_invalid=false)
if test "x$gtksharp_invalid" = "xtrue"; then
AC_MSG_ERROR([gtk-sharp versions between 2.12.2 and 2.12.6 (inclusive) are not supported.])
fi
PKG_PROG_PKG_CONFIG()
AC_SUBST(MCS)
dnl Handle GConf
AC_PATH_PROG(GCONFTOOL, gconftool-2, no)
AM_GCONF_SOURCE_2
AC_OUTPUT([
Makefile
data/Makefile
data/gnome-subtitles.desktop
src/Makefile
src/GnomeSubtitles/Execution/AssemblyInfo.cs
src/GnomeSubtitles/Execution/gnome-subtitles
src/GnomeSubtitles/Execution/ConfigureDefines.cs
help/Makefile
po/Makefile.in])
desktopdir = $(datadir)/applications
desktop_DATA = gnome-subtitles.desktop
gnomesubtitlesicondir = $(datadir)/pixmaps
gnomesubtitlesicon_DATA = gnome-subtitles.png
schemadir = $(GCONF_SCHEMA_FILE_DIR)
schema_DATA = gnome-subtitles.schemas
man_MANS = gnome-subtitles.1
EXTRA_DIST = \
$(desktop_DATA) \
$(gnomesubtitlesicon_DATA) \
$(man_MANS) \
$(schema_DATA)
if GCONF_SCHEMAS_INSTALL
install-data-local:
GCONF_CONFIG_SOURCE=$(GCONF_SCHEMA_CONFIG_SOURCE) $(GCONFTOOL) --makefile-install-rule $(schema_DATA)
endif
This diff is collapsed.
.TH gnome-subtitles "1" "December 3, 2007"
.SH NAME
gnome-subtitles \- video subtitling for the GNOME desktop
.SH SYNOPSIS
.B gnome-subtitles
.RI [ options ]
.br
.SH DESCRIPTION
.B Gnome Subtitles
is a subtitle editor for the GNOME desktop. It supports the most
common text-based subtitle formats and allows for subtitle editing, conversion and
synchronization.
.SH OPTIONS
.TP
\fBfilename\fR
Specifies the subtitle file to open when
.B Gnome Subtitles
starts. If this is not specified, a blank subtitle file will be loaded with the "Unsaved Subtitles" label.
.PP
Gnome Subtitles also obeys all normal GNOME and GTK+ command line options.
.SH BUGS
If you find a bug, please report it at http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-subtitles.
.SH AUTHOR
.B Gnome Subtitles
was written by Pedro Castro <dev@pedrocastro.org>. This manpage was written
by Pedro Castro and Tiago Bortoletto Vaz <tiago@debian-ba.org>.
[Desktop Entry]
Version=1.0
Name=Gnome Subtitles
GenericName=Subtitle Editor
Comment=Video subtitling for the GNOME desktop
TryExec=gnome-subtitles
Exec=gnome-subtitles %f
Icon=gnome-subtitles.png
StartupNotify=true
Terminal=false
Type=Application
Categories=GNOME;GTK;Video;AudioVideo;
MimeType=application/x-subrip;text/x-mpsub;text/x-ssa;text/x-microdvd;
X-GNOME-Bugzilla-Bugzilla=GNOME
X-GNOME-Bugzilla-Product=gnome-subtitles
X-GNOME-Bugzilla-Component=general
X-GNOME-Bugzilla-Version=0.9.1
[Desktop Entry]
Version=1.0
Name=Gnome Subtitles
GenericName=Subtitle Editor
Comment=Video subtitling for the GNOME desktop
TryExec=gnome-subtitles
Exec=gnome-subtitles %f
Icon=gnome-subtitles.png
StartupNotify=true
Terminal=false
Type=Application
Categories=GNOME;GTK;Video;AudioVideo;
MimeType=application/x-subrip;text/x-mpsub;text/x-ssa;text/x-microdvd;
X-GNOME-Bugzilla-Bugzilla=GNOME