Developers

From VikingWiki

Jump to: navigation, search

Contents

Releasing a new version

Build the tarball

Building the tarball is easy with auto-tools. We only need to do:

make dist

Create the release on SourceForge site

The tar ball must be uploaded to SourceForge. This job need two steps.

First one is to upload the tarball on the SourceForge's public ftp:

wput viking-xxx.tar.gz ftp://upload.sourceforge.net/incoming/

Then, on the "File release" section of SourceForge, create the new release via "Add release" link. Fill in the entries, and select the viking-xxx.tar.gz.

Announce the release

There are different media where to announce the new release:

Packaging

Debian

Register to viking-debian mailing-list.

Take a look at Packages overview for The Debian Vikings, which includes a lot of useful informations and links regarding the status of the viking package in Debian, including a link to Build logs on the different Debian architectures.

The packaging files are hosted on the Viking's SVN, in a dedicated subtree.

Gentoo

The packaging files are hosted on the Viking's SVN, in a dedicated subtree.

Internationalization and Localization

(Check a definition on Wikipedia.

Internationalization is a work in progress.

Check Guyou's Git repo about Glib based I18N.

Internationalization

Follow gettext manual.

Main job is to identify translatable strings. Next, we have to decide how to "tag" it:

  • "_(xxx)" if the context allows code execution and dynamic string
  • "N_(xxx)" if we simply want to tag the string but not translate it here (translation will be done later in the program).

Localization

You want to translate Viking into your language?

First thing to do is to generate an up-to-date template PO file. Go to ./po and type:

make viking.pot

Next, use this file in your PO editor (for example, poEdit which can propose some translation).

Links

Personal tools