Re: Some Japanese translation: ja.po
Derek Atkins <[EMAIL PROTECTED]> writes:
> The best way I think to generate an account tree for the accounts
> hierarchy:
>
> 1) create a tree in gnucash
> 2) save it
Or {File > Export > Export Accounts}.
> I think it's probably much easier (and faster) to do it this way than
> to create all the XML by hand.
Probably, yeah.
--
...jsled
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED]
pgpoeRLGoDaRY.pgp
Description: PGP signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Some Japanese translation: ja.po
Josh Sled <[EMAIL PROTECTED]> writes:
> "Hiroto Kagotani" <[EMAIL PROTECTED]> writes:
>> By the way, is there any standard way to translate predefined account
>> set files in accounts dir? In particular, can I add Japanese specific
>> accounts here and how can I define act:id elements?
>
> accounts/${langdir}/ contains the translations available for the account
> trees, including entirely new, perhaps locale-specific account trees (for
> example accounts/de_DE/acctchrt_skr03.gnucash-xea). All installed files are
> enumerated at run time to build the dialog's contents, so simply creating a
> new file (following the same file-name conventions) and adding it to the
> relevant Makefile.am for distribution is sufficient.
>
> I note that there's already an accounts/ja_JP.EUC/, which appears to contain
> the "common" account hierarchy encoded in EUC-JP, but for some reason it's
> not mentioned/distributed in the accounts/Makefile.am.
>
>
> To generate an ID, the most straightforward way is:
>
> [EMAIL PROTECTED] [~]$ uuidgen | tr -d -
> 15fd93733e2549bea5027450082f9b27
The best way I think to generate an account tree for the accounts
hierarchy:
1) create a tree in gnucash
2) save it
3) uncompress it
4) hand-modify the XML to include the proper header and change
the account GUID types from "guid=" to "new="
I think it's probably much easier (and faster) to do it this way than
to create all the XML by hand.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
[EMAIL PROTECTED]PGP key available
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Some Japanese translation: ja.po
"Hiroto Kagotani" <[EMAIL PROTECTED]> writes:
> By the way, is there any standard way to translate predefined account
> set files in accounts dir? In particular, can I add Japanese specific
> accounts here and how can I define act:id elements?
accounts/${langdir}/ contains the translations available for the account
trees, including entirely new, perhaps locale-specific account trees (for
example accounts/de_DE/acctchrt_skr03.gnucash-xea). All installed files are
enumerated at run time to build the dialog's contents, so simply creating a
new file (following the same file-name conventions) and adding it to the
relevant Makefile.am for distribution is sufficient.
I note that there's already an accounts/ja_JP.EUC/, which appears to contain
the "common" account hierarchy encoded in EUC-JP, but for some reason it's
not mentioned/distributed in the accounts/Makefile.am.
To generate an ID, the most straightforward way is:
[EMAIL PROTECTED] [~]$ uuidgen | tr -d -
15fd93733e2549bea5027450082f9b27
--
...jsled
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED]
pgpO7mpK9PPHc.pgp
Description: PGP signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
