[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#489218: marked as done (win32-loader: [INTL:vi] Vietnamese program translation update)



Your message dated Sun, 1 Aug 2010 17:17:55 +0200
with message-id <97b3bb21e64c9df87fd90a4bcedfb11b.squirrel@www.phpnet.org>
and subject line Vietnamese translation is updated, but not activated
has caused the Debian Bug report #489218,
regarding win32-loader: [INTL:vi] Vietnamese program translation update
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
489218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489218
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: win32-loader
Version:
Tags:  l10n patch
Severity: wishlist

The updated Vietnamese translation for the program file: win32-loader

Incidentally, are we using NSIS Unicode [1]? It provides UTF-8 support for Windows installers (and I've added a Vietnamese translation to it).

translated and submitted by:

Clytie Siddall
Vietnamese Free-Software Translation Team
http://vnoss.net/dokuwiki/doku.php?id=projects:l10n

Attachment: win32-loader_l10n_po_vi.po
Description: Binary data



[1] http://www.scratchpaper.com/

--- End Message ---
--- Begin Message ---
Version: 0.6.0~pre3

Hi,

The uptodate Vietnamese translation file is in the win32-loader source
package since 0.6.0~pre3 and has been updated several times since then,
but had never (at least isn't now) been activated, as NSIS lacks
Vietnamese support ("Unicode NSIS" does, but isn't in Debian).

So I am hereby closing this bug; please re-open if you feel it is needed.

Cheers,

OdyX



--- End Message ---

Reply to: