Jump to content

Instructions for making a Language Pack


Recommended Posts

This summarizes what's in the "Official Pdn Localization Topic" so you don't have to read 6+ pages of forum posts :)

Instructions are here:

http://www.getpaint.net/files/loc/2.6/T ... onPack.txt

(These instructions also work for v2.70)

The Paint.NET Blog: https://blog.getpaint.net/

Donations are always appreciated! https://www.getpaint.net/donate.html

forumSig_bmwE60.jpg

Link to post
Share on other sites
  • 1 year later...

I mean many software just load entries from a .ini file or some files they specify the extention name by themselves.

it is very convenient to edit that type of files with notepad.

Below is just an example of language file for Bitcomet. For translators, they just need to edit this file to create another language version. the file will not be compiled into any exe file, just out side, maybe in a directory named "lang"

-------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

-

-

-

新建HTTP/FTP任务(&N) (Ctrl+N)

批é‡

Link to post
Share on other sites
  • 1 year later...
  • 3 weeks later...
  • 2 months later...
  • 4 months later...
In a future version - why not make languages load as dependancies like plugins - rather than compiled into the main assembly? Isn't that more logical?

Just noticed this post again because a spammer was making the rounds -- but anyway, to answer this ...

Language files aren't built-in to the main assembly. They are treated as plugins, in a way. However, from the standpoint of packaging an installer, they are fairly static. If I want to add a language to Paint.NET, that means I need to push out a newly packaged installer EXE. And that means pushing out 1.5mb via the auto-updater and getting all the mirrors (BetaNews, download.com, etc.) to host the new file. It's much more practical to only release new languages with an honestly new version. That way people who won't be using that new language won't be downloading 1.5mb for no benefit.

Adding a feature to the installer, such as, "Choose language file..." to the language choice dropdown, has all sorts of logistical problems of its own. How would a non-English speaker understand what "Choose language file..." means? How would they know where to find the language file in the first place? It just wouldn't scale beyond a small subset of people, and as such would not have much benefit but with the cost of a lot of work/time.

The Paint.NET Blog: https://blog.getpaint.net/

Donations are always appreciated! https://www.getpaint.net/donate.html

forumSig_bmwE60.jpg

Link to post
Share on other sites
  • 2 weeks later...
Adding a feature to the installer, such as, "Choose language file..." to the language choice dropdown, has all sorts of logistical problems of its own. How would a non-English speaker understand what "Choose language file..." means? How would they know where to find the language file in the first place? It just wouldn't scale beyond a small subset of people, and as such would not have much benefit but with the cost of a lot of work/time.

I suggest using a listbox for this, each language could be listed (in its own, of course), with no understanding of the term "language" required.

KaHuc.png
Link to post
Share on other sites
  • 4 months later...
  • 3 years later...
  • 10 months later...
  • 1 year later...
  • 1 year later...

Closed because a new resource has been published.

Link to post
Share on other sites
Guest
This topic is now closed to further replies.
×
×
  • Create New...