+++ /dev/null
-all: status.mdwn
- ikiwiki --setup ikiwiki.setup
-
-%: %.m4
- m4 -P $< >$@
+++ /dev/null
-# Contributing
-
-This page explains how you can contribute to the PostgreSQL
-translation effort.
-
-## Newcomers
-
-If you are new, please check on the [[status]] page whether your
-language is already being worked on. If so, look into the translation
-files near the top to find out where to contact the last translator or
-the translation team. Please contact them about contributing. If the
-last translator cannot be reached or if it has been a long time since
-the last update to the file, you can just take over. But remember
-that communicating first avoids duplicate work later.
-
-In any case, read the [[Howto]] about how to go about filling in the
-translations.
-
-To submit new or updated translation files, submit them to the [Patch
-Tracker](http://pgfoundry.org/tracker/?atid=320&group_id=1000064).
-One of the registered developers will install your file into the
-source code repository. Make sure you specify which branch your file
-is for (see below about branches).
-
-## Registered Developers
-
-People who have contributed for a while will be registered as
-developers and are able to commit their files into the source code
-repository by themselves.
-
-## Release Management
-
-You can work in several branches. There is a current branch and
-several back branches.
-
-The back branches belong to past releases of PostgreSQL. It is
-usually a good idea to finish translations for the recent back
-branches first, because those are the ones that people currently use.
-When a new back branch release is made (something like 8.0.5 or
-8.1.1), updated translations will be included.
-
-By contrast, the current branch is often under heavy development,
-meaning that error messages change, and translation work done today
-might become obsolete tomorrow. Therefore, translations in the
-current branch should normally only be done during the beta phase or
-after a release if no new branch for the development release has been
-made yet. (The [[status]] page informs about the status of the
-branches.)
-
-Information about release schedules and so on will also be posted to
-the mailing list <pgtranslation-translators@pgfoundry.org> (see
-[mailing lists](http://pgfoundry.org/mail/?group_id=1000064)), which
-you are encouraged to read.
+++ /dev/null
-# Howto
-
-Here is how to get set up for translation work. It is assumed here
-that you already know your way around gettext message catalogs. If
-you're new to this, read the chapter on NLS in the PostgreSQL
-Documentation.
-
-## Translating
-
-1. To continue an existing translation, download a new PO file by
- following the links in the [[status]] tables. Fill in the file as
- much as you want.
-
-2. To start a new translation, download a POT file by clicking on one
- of the catalog names in the left column of the [[status]] tables.
- First, fill in all the fields in the header and remove the fuzzy
- flag. Particularly, the character set information is very
- important and must not be left out! Then fill in the rest of the
- file as much as you want.
-
-3. When you are done editing, *check the file* for errors. If you're
- using the Emacs PO mode, press V. From the command line, run
- `msgfmt -o /dev/null -v -c yourfile.po`. Or copy the file into the
- main PostgreSQL source tree and run `gmake maintainer-check-po`.
- If you don't do this, your file might contain bugs that cause
- program crashes, which will quickly disenchant users from
- PostgreSQL and internationalized software in general.
-
-4. Submit the resulting file to the [Patch
- Tracker](http://pgfoundry.org/tracker/?atid=320&group_id=1000064).
- Please do not send patches; send the whole file. If you're
- concerned that the file is too big, run it through a compression
- program. Also, please send each PO file as a separate attachment;
- no tar or zip archives please. Both of these rules make it easier
- for the person installing your files.
-
-## Tools
-
-Please don't edit the PO files with a plain text editor. You're
-making your life unnecessarily hard. There are several tools that
-make editing PO files really easy.
-
-- GNU Emacs and XEmacs have PO editing modes.
-
-- [KBabel](http://i18n.kde.org/tools/kbabel/) is for those who like
- KDE-based tools.
-
-- [poEdit](http://poedit.sourceforge.net) is yet another tool, which
- even works under Windows.
-
-## Tips
-
-Check out the home of the [GNU Translation
-Project](http://www.iro.umontreal.ca/contrib/po/HTML/). There you can
-find out about mailing lists, web sites, and other resources for
-translation efforts to your language. Some of these resources are
-GNU-oriented, but others are not.
+++ /dev/null
-#!/usr/bin/perl
-# Configuration file for ikiwiki.
-# Passing this to ikiwiki --setup will make ikiwiki generate wrappers and
-# build the wiki.
-#
-# Remember to re-run ikiwiki --setup any time you edit this file.
-
-use IkiWiki::Setup::Standard {
- wikiname => "PostgreSQL Translation Project",
- #adminuser => ["yourname", ],
- adminemail => 'peter_e@gmx.net',
-
- # Be sure to customise these..
- srcdir => ".",
- destdir => "../wwwinstall",
-
- url => "http://pgtranslation.projects.postgresql.org/",
- #cgiurl => "http://example.org/ikiwiki.cgi",
- #templatedir => "/usr/share/ikiwiki/templates",
- #underlaydir => "/usr/share/ikiwiki/basewiki",
-
- # Subversion stuff.
- #rcs => "svn",
- #historyurl => "http://svn.example.org/trunk/[[file]]",
- #diffurl => "http://svn.example.org/trunk/[[file]]?root=wiki&r1=[[r1]]&r2=[[r2]]",
- #svnpath => "trunk",
-
- # Git stuff.
- #rcs => "git",
- #historyurl => "http://git.example.org/gitweb.cgi?p=wiki.git;a=history;f=[[file]]",
- #diffurl => "http://git.example.org/gitweb.cgi?p=wiki.git;a=blobdiff;h=[[sha1_to]];hp=[[sha1_from]];hb=[[sha1_parent]];f=[[file]]",
- #gitorigin_branch => "origin",
- #gitmaster_branch => "master",
-
- # Tla stuff.
- #rcs => "tla"
- #historyurl => ??,
- #diffurl => ??,
-
- # Mercurial stuff.
- #rcs => "mercurial",
- #historyurl => "http://localhost:8000/log/tip/[[file]]", # hg serve'd local repository
- #diffurl => "http://localhost:8000/?fd=[[r2]];file=[[file]]",
-
- # Bazaar stuff.
- #rcs => "bzr",
- #historyurl => "",
- #diffurl => "http://example.com/revision?start_revid=[[r2]]#[[file]]-s", # using loggerhead
-
- # Monotone stuff
- #rcs => "monotone",
- #mtnkey => "web\@machine.company.com",
- #historyurl => "http://viewmtn.example.com/",
- #diffurl => "http://viewmtn.example.com/revision/diff/[[r1]]/with/[[r2]]/[[file]]",
- # Set if you want the wiki to sync on update and commit.
- #mtnsync => 0,
- # The path to your workspace (defaults to the srcdir itself)
- # e.g. use if your srcdir is a subdirectory of the workspace.
- #mtnrootdir => "path/to/root/of/workspace",
- # This is a monotone lua hook file used by ikiwiki for
- # inserting conflict markers. By default it will use
- # mtnrootdir/_MTN/mergerc. This hook will be populated with
- # default code the first time you use ikiwiki. You can
- # change it to alter how conflict markers are inserted.
- #mtnmergerc => "path/to/mergerc",
-
- wrappers => [
- #{
- # # The cgi wrapper.
- # cgi => 1,
- # wrapper => "/var/www/wiki/ikiwiki.cgi",
- # wrappermode => "06755",
- #},
- #{
- # # The svn post-commit wrapper.
- # # Note that this will overwrite any existing
- # # post-commit hook script, which may not be
- # # what you want.
- # wrapper => "/svn/wikirepo/hooks/post-commit",
- # wrappermode => "04755",
- # # Log to syslog since svn post-commit hooks
- # # hide output and errors.
- # syslog => 1,
- #},
- #{
- # # The git post-update wrapper.
- # # Note that this will overwrite any existing
- # # post-update hook script, which may not be
- # # what you want.
- # wrapper => "/git/wiki.git/hooks/post-update",
- # wrappermode => "06755",
- #},
- ],
-
- # Default to generating rss feeds for blogs?
- rss => 1,
- # Default to generating atom feeds for blogs?
- atom => 1,
- # Allow generating feeds even if not generated by default?
- #allowrss => 1,
- #allowatom => 1,
- # Urls to ping with XML-RPC when rss feeds are updated
- #pingurl => [qw{http://rpc.technorati.com/rpc/ping}],
- # Include discussion links on all pages?
- discussion => 1,
- # To exclude files matching a regexp from processing. This adds to
- # the default exclude list.
- exclude => qr/\.m4/,
- # To change the extension used for generated html files.
- #htmlext => 'htm',
- # Time format (for strftime)
- timeformat => '%F %T',
- # Locale to use. Must be a UTF-8 locale.
- #locale => 'en_US.UTF-8',
- # Only send cookies over SSL connections.
- #sslcookie => 1,
- # Logging settings:
- #verbose => 1,
- syslog => 0,
- # To link to user pages in a subdirectory of the wiki.
- #userdir => "users",
- # To create output files named page.html rather than page/index.html.
- #usedirs => 0,
- # Simple spam prevention: require an account-creation password.
- #account_creation_password => "example",
- # Uncomment to force ikiwiki to run with a particular umask.
- #umask => 022,
- # Default settings for the recentchanges page.
- #recentchangespage => "recentchanges",
- #recentchangesnum => 100,
-
- # To add plugins, list them here.
- #add_plugins => [qw{goodstuff search wikitext camelcase
- # htmltidy fortune sidebar map rst anonok}],
- add_plugins => [qw{goodstuff embed inline smiley favicon rawhtml sidebar}],
- # If you want to disable any of the default plugins, list them here.
- #disable_plugins => [qw{inline htmlscrubber passwordauth openid}],
- # To add a directory to the perl search path, use this.
- #libdir => "/home/me/.ikiwiki/",
-
- # For use with the tag plugin, make all tags be located under a
- # base page.
- #tagbase => "tag",
-
- # For use with the search plugin if your estseek.cgi is located
- # somewhere else.
- #estseek => "/usr/lib/estraier/estseek.cgi",
-
- # For use with the openid plugin, to give an url to a page users
- # can use to signup for an OpenID.
- #openidsignup => "http://myopenid.com/",
-
- # For use with the mirrorlist plugin, a list of mirrors.
- #mirrorlist => {
- # mirror1 => "http://hostname1",
- # mirror2 => "http://hostname2/mirror",
- #},
-}
+++ /dev/null
-# PostgreSQL Translation Project
-
-This page contains some information about the PostgreSQL National
-Language Support effort. Please read the [information about NLS in
-the PostgreSQL
-Documentation](http://developer.postgresql.org/docs/postgres/nls.html)
-for background and technical information. Some of the information on
-this page may eventually be migrated there as it stabilizes. There's
-also the [GNU Gettext
-Manual](http://www.gnu.org/manual/software/gettext/html_chapter/gettext_toc.html),
-which is only partially relevant for us, but it might be good to look
-at anyway.
-
-## Status
-
-The [[status]] tables shows which areas of the PostgreSQL source are
-prepared for translation, and the progress of those translations.
-There you can also download freshly baked PO files that are merged up
-against the latest program sources. No PostgreSQL source tree is
-needed for translation work.
-
-
-## Communicating
-
-If you have any questions about the PostgreSQL translation project,
-including
-
-- you want to start a new translation or continue an existing one and
- you want to avoid duplicating your work with someone else,
-
-- you're looking for other people who want to work with you on
- translating,
-
-- you're having technical questions about tools, the source tree, the
- meaning of terms, etc.,
-
-then write to the mailing list
-<pgtranslation-translators@pgfoundry.org>. More information about our
-[mailing lists](http://pgfoundry.org/mail/?group_id=1000064) is
-available.
+++ /dev/null
-BODY {
- margin: 0;
-}
-
-H1 {
- color: #EC5800;
-}
-
-H2 {
- border-bottom: solid 10px #0092C3;
-}
-
-#content {
- padding-left: 1em;
- padding-right: 1em;
-}
-
-.note {
- background-color: #F5F5F5;
- margin: 1ex 3ex;
- padding: 0.5ex 1ex;
- border: solid 1px #EFEFEF;
-}
-
-#sidebar {
- background-color: #0092C3;
-}
-
-div#sidebar a {
- color: white;
-}
+++ /dev/null
-- [[Index]]
-- [[Status]]
-- [[Howto]]
-- [[Contributing]]
-- [PgFoundry site](http://www.pgfoundry.org/projects/pgtranslation/)
+++ /dev/null
-m4_changequote({,})m4_dnl
-# NLS Status Tables
-
-The tables below shows which areas of the PostgreSQL source are
-prepared for translation, and the progress of those translations. The
-numbers are percents of translated messages. By following the links,
-you can download freshly baked PO files that are merged up against the
-latest program sources. No PostgreSQL source tree is needed for
-translation work.
-
-You can work in several branches. Please follow the rumors on the
-hackers list about when a branch is about to be released. Also note
-that working on the current branch might on occasion be a waste of
-time if some developer is planning to rewrite most of the message
-handling, for example. Please check on the hackers list first. When
-you submit updates, please specify the branch.
-
-[[toc levels="2"]]
-
-m4_sinclude(statustables/table-current.html)
-m4_sinclude(statustables/table-8.3-branch.html)
-m4_sinclude(statustables/table-8.2-branch.html)
-m4_sinclude(statustables/table-8.1-branch.html)
-m4_sinclude(statustables/table-8.0-branch.html)
-m4_sinclude(statustables/table-7.4-branch.html)
projects / pgtranslation / admin.git / commitdiff