You must login to post a comment. Don't have an account? Register to get one!

• 

  • #7

  LokiCoyote Sat, 29 Nov 2008 22:10:57

  Right now I don't know of a way to allow you to just modify the Locale files. Hopefully they will add that in the future, real-soon-now.

• 

  • #6

  yeachan Mon, 24 Nov 2008 05:45:38

  Is there a easier way to commit the translation such as adding me into the svn project?

• 

  • #5

  LokiCoyote Mon, 24 Nov 2008 00:41:55

  Thank you. I've updated LibUserScript-1.0.lua and retagged PhotoOp as v0.8.6.1 (v0.8.5.1 might accidentally show up).

  There are also 5 other strings that got added to PhotoOp\Locales\enUS.lua since v0.6.0. They relate to warnings or errors, so they probably aren't a high priority.

• 

  • #4

  yeachan Sun, 23 Nov 2008 06:02:48

  Finally,I finished it.Here is the file and I have it changed into Utf-8 code,so it can work in the Chinese client. http://chineselocal.googlecode.com/files/LibUserScript-1.0.lua

• 

  • #3

  LokiCoyote Sun, 23 Nov 2008 03:45:27

  Basically those are the strings that need to be translated.

  If you want an example look in the "PhotoOp_Options\Libs\AceDBOptions-3.0\AceDBOptions-3.0.lua" file (that's its packaged location).

  Basically we'll be adding something along these lines:

  local LOCALE = GetLocale()
  if LOCALE == "zhCN" then
       -- Localization pretty much as if you were creating an zhCN.lua file
       L["advanced"] = translation of advanced key above
       L["advanced-desc"] = translation of advanced-desc key above
       -- rest of the localization follows
  elseif LOCALE == "zhTW" then
       -- Localization pretty much as if you were creating an zhTW.lua file
       L["advanced"] = translation of advanced key above
       L["advanced-desc"] = translation of advanced-desc key above
       -- rest of the localization follows
  end

  So that anything that is not changed will still have the english text. It doesn't produce as nice an error message as when something gets left out when using AceLocale-3.0, but it works.

  Looking through libraries, they usually do something similar to be self contained / minimal. The only reason this needs translating is that the library creates part of the options configuration.

  This might be a good reason to move the configuration out of the library incidentally...

• 

  • #2

  yeachan Sun, 23 Nov 2008 03:12:57

  I have never translated a lib file,so what do I need to begin my localization part with to replace "local L = {"  ?

• 

  • #1

  LokiCoyote Sun, 23 Nov 2008 00:33:43

  Thanks you, I included your work in alpha r127.

  Most of the localizations are used in the options and are now found in PhotoOp_Options\Locales. I split the files as appropriate.

  It looks like you were using v0.6.0. If you look in the Libs\LibSimpleScript-1.0\Locales, there's another set of strings that need translating, if you are interested.

  However, the current version has a few more strings and the library is now called LibUserScript-1.0. It doesn't use AceLocale, but a simple table. If the LibUserScript-1.0.lua (or LibSimpleScript-1.0\Locales\enUS.lua) file is modified, I can include the changes for release. Specifically the major changes include the addition of an "Advanced" tab.