>> (4) If translators find msgids of locale specific reports should not >> be translated, some common >> words like "Account" are translated on locale specific reports and >> they can't avoid it. >> >> I attach an example of a US tax report with LANG=ja, and you will >> understand what is strange. >> Would you please consider it? >> > > Just as a point of clarification based on your comment on the > attachment: the US Tax Report is not intended to be a report that is > filed with tax authorities in the form it comes out of gnucash. It is > intended to be a report that provides the tax information, with full > audit trail, that is then used by a gnucash user as a source document > for filling out the actual forms (whether manually or with the aid of > separate tax preparation software) that are then filed with the tax > authorities. The tax authorities would never see the gnucash report, > unless you were later audited and wanted to use it to show where you > got the numbers from.
I misunderstood that GnuCash tax reports are submitted to tax authorities. If it is not for tax authorities, this is not major problem. If strings are already frozen for 2.4.0, I think it is reasonable to postpone correcting it. _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
