README
******

   The program ccd2cue is a CCD sheet to CUE sheet converter.  It
supports the full extent of CUE sheet format expressiveness, including
mixed-mode discs and CD-Text meta-data.

   This is the README file for ccd2cue version 0.2.

   Copyright © 2010, 2013 Bruno Félix Rezende Ribeiro

     Permission is granted to copy, distribute and/or modify this
     document under the terms of the GNU Free Documentation License,
     Version 1.3 or any later version published by the Free Software
     Foundation; with no Invariant Sections.  A copy of the license is
     included in the file ‘COPYING.DOC’.


— Table of Contents —
README
Preface
1 Distribution
2 Getting a copy
3 Getting in touch
4 Bug reporting
5 Contributing
6 Donating
7 Hacking


Preface
*******

   This document briefly explains the rules of distribution of this
program(1) and its documentation, how to contact the community, how to
fill bug reports, how to contribute to the project and how to get
started hacking the code.  If you have checked out the source tree from
the CVS repository see *note Hacking::.  For other information about
this package you can check the following files found in the top level
directory of the distribution:

‘INSTALL’
     Generic build and installation instructions;
‘NEWS’
     User-visible changes since previous versions;
‘AUTHORS’
     List of major contributors;
‘THANKS’
     List of minor contributors;
‘TODO’
     Features we want to see implemented someday;
‘DONORS’
     People who supported the development by donations;
‘ABOUT-NLS’
     Internationalization and localization matters;
‘COPYING’
     The program license;
‘COPYING.DOC’
     The documentation license;
‘ChangeLog’
     Detailed list of changes of the source code;

   Information about the GNU operating system, the GNU Project and the
Free Software Movement are included in the distribution — for your
pleasure — in the form of some articles by Richard Stallman (RMS). See
the top-level files:

‘GNU’
     The GNU Manifesto;
‘THE-GNU-PROJECT’
     The GNU Project history;
‘LINUX-GNU’
     Linux and the GNU system;
‘WHY-FREE’
     Why Software Should Not Have Owners;

   For more information about this program you can visit its home page
at <http://www.nongnu.org/ccd2cue/>.  If you want to receive
notifications about new releases of this program or important issues
related to it, subscribe to the mailing list, as described in *note
Getting in touch::, or subscribe to the project atom feed
<https://savannah.nongnu.org/news/atom.php?group=ccd2cue>.

   ---------- Footnotes ----------

   (1) The expression “this program” is used throughout the
documentation to reference the whole software included in the same
package as this file.

1 Distribution
**************

   This program is "free software"; this means that everyone is free to
use it and free to redistribute it under certain conditions.  This
program is not in the public domain; it is copyrighted and there are
restrictions on its distribution, but these restrictions are designed to
permit everything that a good cooperating citizen would want to do.
What is not allowed is to try to prevent others from further sharing any
version of this program that they might get from you.  The precise
conditions are found in the GNU General Public License (‘COPYING’ file).
The program manual is covered by the GNU Free Documentation License
(‘COPYING.DOC’ file).  This license is similar in spirit to the GNU
General Public License, but is more suitable for documentation.

2 Getting a copy
****************

   One way to get a copy of this program is from someone else who has
it.  You need not ask for our permission to do so, or tell any one else;
just copy it.  You may also receive this program when you buy a
computer.  Computer manufacturers are free to distribute copies on the
same terms that apply to everyone else.  These terms require them to
give you the full sources, including whatever changes they may have
made, and to permit you to redistribute the program received from them
under the usual terms of the GNU General Public License.  In other
words, the program must be free for you when you get it, not just free
for the manufacturer.

   If you have access to the Internet, you can get the latest
distribution version of this program at
<http://download.savannah.gnu.org/releases/ccd2cue/>.  Please, use a
mirror if possible; you will be automatically redirected to the nearest
mirror at <http://download-mirror.savannah.gnu.org/releases/ccd2cue/>.

   A CVS repository, where the development takes place, is also
available.  It maintains the full history of modifications of every
single source file.  You can checkout any given revision of any file or
get a snapshot of the entire source tree in a particular desired state.
Special build tools, as described in *note Hacking::, are required to
build from those checkouts, though.  Notably, to stay up to date with
the latest developments in the source tree, you can anonymously checkout
the repository with the following command:
     cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:\
     /sources/ccd2cue co ccd2cue

3 Getting in touch
******************

   You can get in touch with other users and the developers of this
program subscribing to the mailing list.  Anyone is welcome to join the
list; to do so, visit
<http://lists.nongnu.org/mailman/listinfo/ccd2cue-bug/> or send an email
to <ccd2cue-bug-join@nongnu.org>.  You can use this list for all
discussion, including asking for help and bug reporting, although the
preferred method for reporting bugs is the dedicated bug tracking web
interface described in *note Bug reporting::.  To post a message to all
the list members, send email to <ccd2cue-bug@nongnu.org>.  To see the
collection of prior postings to the list, visit its archive at:
<http://lists.nongnu.org/archive/html/ccd2cue-bug/>.

   If you feel somewhat chatty, eager for a somewhat more instantaneous
response from community, you can join us on our friendly IRC channel:
     #ccd2cue at freenode.net

4 Bug reporting
***************

   If you come across some problem and need help you can contact the
community as described *Note Getting in touch::.  If you think you found
a bug, but is not quite sure about it, you can instead ask for support
on our support tracker at
<https://savannah.nongnu.org/support/?group=ccd2cue>.  We will revise
your post, advise you and take the appropriate measures.  If you are
confident you have found a bug, you can submit a bug report directly at
our bug tracker: <https://savannah.nongnu.org/bugs/?group=ccd2cue>.
Please, when reporting a bug include enough information for the
maintainers to reproduce the problem.  Generally speaking, that means:

   • The contents of any input files necessary to reproduce the bug and
     command line invocations of the program(s) involved (crucial!).
   • A description of the problem and any samples of the erroneous
     output.
   • The version number of the program(s) involved (use ‘--version’).
   • Hardware, operating system, and compiler versions (‘uname -a’).
   • Unusual options you gave to configure, if any (see
     ‘config.status’).
   • Anything else that you think would be helpful.

5 Contributing
**************

   This program is a collaborative project and we encourage
contributions from anyone and everyone — your help is very much
appreciated.  You can help in many ways:

   • Donate to developers in order to support their work.  See *note
     Donating::.
   • Write documentation.  We are specially in need to complete the CCD
     sheet format specification.
   • Help users in the mailing list and IRC channel.
   • Find and report bugs.  *Note Bug reporting::.
   • Fix reported bugs.
   • Implement new feature ideas.
   • Write test cases.
   • Check the documentation against the implementation.
   • Translate the program strings to other languages.

   You can join the development team to contribute code and
documentation at <https://savannah.nongnu.org/projects/ccd2cue/>.
Patches are most welcome, but contributed code should follow the GNU
Coding Standards.  *Note (standards)::.  If it doesn’t, we’ll need to
find someone to fix the code before we can use it.  It is also necessary
that the contributor be willing to assign their copyright to the FSF
(Free Software Foundation), since the developers plan to make it
officially part of the GNU operating system and they want FSF to enforce
the program’s license.  To get started hacking see *note Hacking::.

6 Donating
**********

   If you find this program useful, please *send a donation* to its
developers to support their work.  If you use this program at your
workplace, please suggest that the company make a donation.  We
appreciate contributions of any size – donations enable us to spend more
time working on the project, and help cover our infrastructure expenses.

   If you’d like to make a donation of any value, please send it to the
following Bitcoin address:

     12sKDaBNYekQuRPdrpnbUL4YRDKrzMnY62

   Since our project isn’t a tax-exempt organization, we can’t offer you
a tax deduction, but for all donations over 0.05 BTC, we’d be happy to
recognize your contribution on <http://www.nongnu.org/ccd2cue/donors/>
and on ‘DONORS’ file for the next release.

   We are also happy to consider making particular improvements or
changes, or giving specific technical assistance, in return for a
substantial donation over 0.5 BTC. If you would like to discuss this
possibility, write to us at <ccd2cue-support@nongnu.org>.

   Another possibility is to pay a software maintenance fee.  Again,
write to us about this at <ccd2cue-support@nongnu.org> to discuss how
much you want to pay and how much maintenance we can offer in return.

                      *Thanks for your support!*

7 Hacking
*********

The development sources are available through CVS at Savannah:

     https://savannah.nongnu.org/cvs/?group=ccd2cue

   If you are getting the sources from CVS (or change ‘configure.ac’),
you’ll need to have Automake, Autoconf and Gettext installed to
(re)build.  You’ll also need help2man.  All of these programs are
available from <ftp://ftp.gnu.org/gnu>.

   After getting the CVS sources, and installing the tools above, you
can run ‘./bootstrap’ to do a fresh build.  After that first time,
running ‘make’ should suffice.  See file ‘INSTALL’.

   When modifying the sources, or making a distribution, more is needed,
as follows:

   • This distribution also uses Gnulib
     (<http://www.gnu.org/software/gnulib>) to share common files,
     stored as a submodule in git.
   • When updating gettext, besides the normal installation on the
     system, it is necessary to run ‘gettextize -f’ in this hierarchy to
     update the ‘po/’ infrastructure.  After doing so, rerun
     ‘gnulib-tool --import’ since otherwise older files will have been
     imported.  *Note (gnulib)::, for more information.
