--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/AUTHORS Sun Sep 12 17:02:13 2010 +0200
@@ -0,0 +1,3 @@
+Nora Petrova
+Ai Rosmalia
+Guido Berhoerster
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/COPYING Sun Sep 12 17:02:13 2010 +0200
@@ -0,0 +1,83 @@
+The files data/blue-sky.jpg, data/openindiana-default.jpg, data/sparkle.jpg,
+data/purple-haze.jpg are distributed under the following
+terms:
+
+Copyright 2010 Nora Petrova <[email protected]>. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY NORA PETROVA ``AS IS'' AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL NORA PETROVA OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+The views and conclusions contained in the software and documentation are those
+of the authors and should not be interpreted as representing official policies,
+either expressed or implied, of Nora Petrova.
+
+The files data/daisy.jpg and data/dandelion.jpg are distributed under the
+following terms:
+
+Copyright (c) 2010 Ai Rosmalia. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+Unless otherwise noted the remaining files are distributed under the following
+terms:
+
+Copyright (c) 2010 Guido Berhoerster. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/INSTALL Sun Sep 12 17:02:13 2010 +0200
@@ -0,0 +1,291 @@
+Installation Instructions
+*************************
+
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006, 2007, 2008 Free Software Foundation, Inc.
+
+ This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+
+Basic Installation
+==================
+
+ Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package. The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.
+
+ 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 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.
+
+ Running `configure' might take a while. 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.
+
+ 6. Often, you can also type `make uninstall' to remove the installed
+ files again.
+
+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=c99 CFLAGS=-g 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 can use 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 `..'.
+
+ With a non-GNU `make', it is safer 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.
+
+ On MacOS X 10.5 and later systems, you can create libraries and
+executables that work on multiple system types--known as "fat" or
+"universal" binaries--by specifying multiple `-arch' options to the
+compiler but only a single `-arch' option to the preprocessor. Like
+this:
+
+ ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+ CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+ CPP="gcc -E" CXXCPP="g++ -E"
+
+ This is not guaranteed to produce working output in all cases, you
+may have to build one architecture at a time and combine the results
+using the `lipo' tool if you have problems.
+
+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.
+
+Particular systems
+==================
+
+ On HP-UX, the default C compiler is not ANSI C compatible. If GNU
+CC is not installed, it is recommended to use the following options in
+order to use an ANSI C compiler:
+
+ ./configure CC="cc -Ae"
+
+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
+
+ On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
+parse its `<wchar.h>' header file. The option `-nodtk' can be used as
+a workaround. If GNU CC is not installed, it is therefore recommended
+to try
+
+ ./configure CC="cc"
+
+and if that doesn't work, try
+
+ ./configure CC="cc -nodtk"
+
+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).
+
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
+an Autoconf bug. Until the bug is fixed you can use this workaround:
+
+ CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+`configure' Invocation
+======================
+
+ `configure' recognizes the following options to control how it
+operates.
+
+`--help'
+`-h'
+ Print a summary of all of the options to `configure', and exit.
+
+`--help=short'
+`--help=recursive'
+ Print a summary of the options unique to this package's
+ `configure', and exit. The `short' variant lists options used
+ only in the top level, while the `recursive' variant lists options
+ also present in any nested packages.
+
+`--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.
+
+`--prefix=DIR'
+ Use DIR as the installation prefix. *Note Installation Names::
+ for more details, including other options available for fine-tuning
+ the installation locations.
+
+`--no-create'
+`-n'
+ Run the configure checks, but stop before creating any output
+ files.
+
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/Makefile.am Sun Sep 12 17:02:13 2010 +0200
@@ -0,0 +1,25 @@
+### Process this file with automake to produce Makefile.in
+
+EXTRA_DIST = \
+ autogen.sh \
+ ChangeLog \
+ intltool-extract.in \
+ intltool-merge.in \
+ intltool-update.in
+
+DISTCLEANFILES = \
+ intltool-extract \
+ intltool-merge \
+ intltool-update
+
+ChangeLog: $(srcdir)/ChangeLog
+
+$(srcdir)/ChangeLog:
+ if hg tip >/dev/null 2>&1; then \
+ hg log --style changelog >$@; \
+ else \
+ echo "could not generate ChangeLog" >&2; \
+ echo "The changelog coud not be generated." >ChangeLog; \
+ fi
+
+SUBDIRS = po data
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/autogen.sh Sun Sep 12 17:02:13 2010 +0200
@@ -0,0 +1,56 @@
+#!/bin/sh
+
+error_msg () {
+ printf "%s\n" "$@" >&2
+}
+
+if [ ! -f ./data/openindiana-backgrounds.xml.in.in ]; then
+ error_msg "this script must be executed from the root directory of the openindiana-welcome distribution"
+ exit 1
+fi
+
+if ! gettext_version="$(autopoint --version 2>/dev/null | head -1)"; then
+ error_msg "autopoint not found, please install gettext and ensure that autopoint is in PATH"
+ exit 1
+fi
+
+if ! intltool_version="$(intltoolize --version 2>/dev/null | head -1)"; then
+ error_msg "intltoolize not found, please install intltool and ensure that intltoolize is in PATH"
+ exit 1
+fi
+
+if ! autoconf_version="$(autoconf --version 2>/dev/null | head -1)"; then
+ error_msg "autoconf not found, please install autoconf and ensure that autoconf is in PATH"
+ exit 1
+fi
+
+if ! autoheader_version="$(autoheader --version 2>/dev/null | head -1)"; then
+ error_msg "autoheader not found, please install autoheader and ensure that autoheader is in PATH"
+ exit 1
+fi
+
+if ! automake_version="$(automake --version 2>/dev/null | head -1)"; then
+ error_msg "automake not found, please install automake and ensure that automake is in PATH"
+ exit 1
+fi
+
+cat <<EOF
+ Buildsystem summary
+ ===================
+
+ Gettext: $gettext_version
+ Intltool: $intltool_version
+ Autoconf: $autoconf_version
+ Autoheader: $autoheader_version
+ Automake: $automake_version
+
+EOF
+
+set -e
+autopoint --force $AP_OPTS
+intltoolize --force --copy --automake
+aclocal -I m4 --install $AL_OPTS
+autoconf $AC_OPTS
+autoheader $AH_OPTS
+automake --add-missing --copy $AM_OPTS
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/configure.ac Sun Sep 12 17:02:13 2010 +0200
@@ -0,0 +1,30 @@
+dnl Process this file with autoconf to produce a configure script.
+
+AC_PREREQ([2.63])
+AC_INIT([openindiana-backgrounds],
+ [0.1],
+ [https://bugs.launchpad.net/openindiana],
+ [openindiana-backgrounds],
+ [http://openindiana.org/])
+AM_INIT_AUTOMAKE([foreign tar-ustar dist-bzip2])
+AM_MAINTAINER_MODE
+AC_CONFIG_SRCDIR([data/openindiana-backgrounds.xml.in.in])
+
+AC_PROG_INSTALL
+AC_PROG_SED
+IT_PROG_INTLTOOL([0.40.0])
+
+GETTEXT_PACKAGE=openindiana-backgrounds
+AC_SUBST(GETTEXT_PACKAGE)
+AC_DEFINE_UNQUOTED(GETTEXT_PACKAGE,
+ "${GETTEXT_PACKAGE}",
+ [the gettext translation domain])
+AM_GNU_GETTEXT([external])
+AM_GNU_GETTEXT_VERSION([0.17])
+
+AC_CONFIG_HEADERS([config.h])
+AC_CONFIG_FILES([Makefile
+ po/Makefile.in
+ data/Makefile])
+AC_OUTPUT
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/data/Makefile.am Sun Sep 12 17:02:13 2010 +0200
@@ -0,0 +1,32 @@
+### Process this file with automake to produce Makefile.in
+
+backgrounddir = $(datadir)/pixmaps/backgrounds/openindiana
+
+background_DATA = \
+ openindiana-default.jpg \
+ blue-sky.jpg \
+ sparkle.jpg \
+ purple-haze.jpg \
+ daisy.jpg \
+ dandelion.jpg
+
+metadata_in_files = openindiana-backgrounds.xml.in
+metadatadir = $(datadir)/gnome-background-properties
+metadata_DATA = $(metadata_in_files:.xml.in=.xml)
+@INTLTOOL_XML_RULE@
+
+noinst_DATA = openindiana-backgrounds.xml.in
+
+CLEANFILES = \
+ openindiana-backgrounds.xml \
+ openindiana-backgrounds.xml.in
+
+DISTCLEANFILES = $(CLEANFILES)
+
+EXTRA_DIST = \
+ $(background_DATA) \
+ openindiana-backgrounds.xml.in.in
+
+openindiana-backgrounds.xml.in: openindiana-backgrounds.xml.in.in Makefile
+ $(SED) 's|%%DATADIR%%|$(datadir)|g' $< >$@
+
Binary file data/blue-sky.jpg has changed
Binary file data/daisy.jpg has changed
Binary file data/dandelion.jpg has changed
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/data/openindiana-backgrounds.xml.in.in Sun Sep 12 17:02:13 2010 +0200
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE wallpapers SYSTEM "gnome-wp-list.dtd">
+<wallpapers>
+ <wallpaper deleted="false">
+ <_name>OpenIndiana Default Wallpaper</_name>
+ <filename>%%DATADIR%%/pixmaps/backgrounds/openindiana/openindiana-default.jpg</filename>
+ <options>zoom</options>
+ </wallpaper>
+ <wallpaper deleted="false">
+ <_name>Blue Sky</_name>
+ <filename>%%DATADIR%%/pixmaps/backgrounds/openindiana/blue-sky.jpg</filename>
+ <options>zoom</options>
+ </wallpaper>
+ <wallpaper deleted="false">
+ <_name>Daisy</_name>
+ <filename>%%DATADIR%%/pixmaps/backgrounds/openindiana/daisy.jpg</filename>
+ <options>zoom</options>
+ </wallpaper>
+ <wallpaper deleted="false">
+ <_name>Dandelion</_name>
+ <filename>%%DATADIR%%/pixmaps/backgrounds/openindiana/dandelion.jpg</filename>
+ <options>zoom</options>
+ </wallpaper>
+ <wallpaper deleted="false">
+ <_name>Sparkle</_name>
+ <filename>%%DATADIR%%/pixmaps/backgrounds/openindiana/sparkle.jpg</filename>
+ <options>zoom</options>
+ </wallpaper>
+ <wallpaper deleted="false">
+ <_name>Purple Haze</_name>
+ <filename>%%DATADIR%%/pixmaps/backgrounds/openindiana/purple-haze.jpg</filename>
+ <options>zoom</options>
+ </wallpaper>
+</wallpapers>
+
Binary file data/openindiana-default.jpg has changed
Binary file data/purple-haze.jpg has changed
Binary file data/sparkle.jpg has changed
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/po/LINGUAS Sun Sep 12 17:02:13 2010 +0200
@@ -0,0 +1,2 @@
+# please keep this list sorted alphabetically
+#
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/po/Makevars Sun Sep 12 17:02:13 2010 +0200
@@ -0,0 +1,41 @@
+# Makefile variables for PO directory in any package using GNU gettext.
+
+# Usually the message domain is the same as the package name.
+DOMAIN = $(PACKAGE)
+
+# These two variables depend on the location of this directory.
+subdir = po
+top_builddir = ..
+
+# These options get passed to xgettext.
+XGETTEXT_OPTIONS = --keyword=_ --keyword=N_
+
+# This is the copyright holder that gets inserted into the header of the
+# $(DOMAIN).pot file. Set this to the copyright holder of the surrounding
+# package. (Note that the msgstr strings, extracted from the package's
+# sources, belong to the copyright holder of the package.) Translators are
+# expected to transfer the copyright for their translations to this person
+# or entity, or to disclaim their copyright. The empty string stands for
+# the public domain; in this case the translators are expected to disclaim
+# their copyright.
+COPYRIGHT_HOLDER = The OpenIndiana Project
+
+# This is the email address or URL to which the translators shall report
+# bugs in the untranslated strings:
+# - Strings which are not entire sentences, see the maintainer guidelines
+# in the GNU gettext documentation, section 'Preparing Strings'.
+# - Strings which use unclear terms or require additional context to be
+# understood.
+# - Strings which make invalid assumptions about notation of date, time or
+# money.
+# - Pluralisation problems.
+# - Incorrect English spelling.
+# - Incorrect formatting.
+# It can be your email address, or a mailing list address where translators
+# can write to without being subscribed, or the URL of a web page through
+# which the translators can contact you.
+MSGID_BUGS_ADDRESS = http://openindiana.org/
+
+# This is the list of locale categories, beyond LC_MESSAGES, for which the
+# message catalogs shall be used. It is usually empty.
+EXTRA_LOCALE_CATEGORIES =
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/po/POTFILES.in Sun Sep 12 17:02:13 2010 +0200
@@ -0,0 +1,1 @@
+data/openindiana-backgrounds.xml.in.in
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/po/POTFILES.skip Sun Sep 12 17:02:13 2010 +0200
@@ -0,0 +1,1 @@
+data/openindiana-backgrounds.xml.in
