4,076

(5 replies, posted in Misc. Charts of Accounts)

Please compare the latest sql/en_US-new.sql with the official Canadian CoA pkg for field order errors before using it.

4,077

(154 replies, posted in Modules Add-on's)

In modules/import_transactions/includes/import_transactions.inc replace line:

if ($person_id != null)

with

if (!empty($person_id))

In modules/import_transactions/import_transactions.php replace line:

$prev_ref = 9999;

with

$prev_ref = -1;

so that a practically impossible value is used for initialisation.

My Unofficial GitHub repo has been updated with white space fixes as well and the extra comma in the last line of templates/payment_en_GB.csv has been eliminated.

You may also further put in the constants for balance of $type == 0, 1, 2 comparisons.

The last line in templates/payment_en_GB.csv has an extra comma at the very end that needs to be removed.

REF2,16/12/14,Paid Creditor Control account 2100,220,2100,0,,,1,1,,

should be

REF2,16/12/14,Paid Creditor Control account 2100,220,2100,0,,,1,1,

4,079

(7 replies, posted in FA Modifications)

Atleast we now can see how the letters play out on the screen. Thanks.

The reason why the standard English letters are preferred to be used (though not intuitive in the non latin languages) is that they can follow the help pages uniformly and it is easier to type just one key as opposed to possibly multiple keys in other languages. Try it out by placing the "&" character preceding (or succeeding in case of RTL language characters) whichever key you wish to use.

Make sure you do a "FLUSH PRIVILEGES;" before proceeding.

4,081

(7 replies, posted in FA Modifications)

Append "&B" to the PO file and recompile it.
The only Arabic I see is ar_EG in the official languages.

Attached is a recompilation with some of the &B / &C elements added to the right of the translations since this is a RTL script. Try it and provide feedback. It will be useful to the devs to alter non latin scripts to accommodate such uniform access keys irrespective of the language.

4,082

(17 replies, posted in Report Bugs here)

Paste the contents of the file lang/languages_installed.inc

Do you have access to the linux command line interface? If so, paste the output of the command:

locale -a

If the German language is not present (de_DE), then enable it with:

sed -i -e 's/# de_DE UTF-8/de_DE UTF-8/' /etc/locale.gen
dpkg-reconfigure --frontend=noninteractive locales

Read the Wiki.

4,083

(11 replies, posted in Reporting)

There are some Win 8.1 compatibility issues with Dot Matrix Printer (DMP) drivers:
Oki / Epson. Location of Update.

Using the Generic Text Only Printer Driver to generate the documents before printing to DMPs may be an option.

Check this link as well.

1. Create a Supplier
2. If your Supplier Currency is different from the home currency, then see that you have an exchange rate acquired for it.
3. Create an Item supplied by the supplier (possibly with prices populated)
4. Create a Purchase Invoice for the Item from the Supplier and get it into your stock (Direct Purchase Invoice is the easiest)

If you still cannot create the Purchase Invoice, then try to create a company with the en_US-demo.sql and see if you can create a supplier invoice there for an existing supplier and revert.

4,085

(7 replies, posted in FA Modifications)

The language translation files for Arabic did not include the English shortcuts as you may want to use some other letter in Arabic instead of &B.... in English. If you still wish to retain the English Access keys then encode it to precede the Arabic language text translation and compile your Arabic .mo file accordingly.

If the said elax_tax_support_files are not proprietary / commercial you can post it here for peer review and possible inclusion into the core.

Which version of FA and Chart of Accounts are you using?

Your costing tables and inventory movements too may need to be changed.

4,089

(17 replies, posted in Report Bugs here)

Check the locales installed in the linux server. you may have to go to the linux command line interface (PuTTY, Terminal, etc) and issue commands for including the german locale.

@elax's 0VAT fix is not part of the core. Where is elax's 0VAT fix and when and where is it used?

4,091

(7 replies, posted in FA Modifications)

What Access key do you mean? Is it a translatable string that is present in Arabic as some unprintable characters? Does the "Access key" re-appear when you switch back to English?

4,092

(17 replies, posted in Report Bugs here)

Compare the backups and check the changes that may have occurred to the sys_prefs table records for default language.
It is also possible that someone de-activated the German language from the lang/installed_languages.inc file.

Extension: rep_tax_cash_basis
Author: Alastair Robertson (KwikPay, NZ)

Lines 166 and 193 in the file modules/rep_tax_cash_basis/includes/tax_cash_db.inc :

            ttd.amount*ex_rate collectible,

should be:

            -1*ttd.amount*ex_rate collectible, 

Kindly verify and revert.

Patch:

--- modules/rep_tax_cash_basis/includes/tax_cash_db.inc    Mon Oct 14 01:44:10 2013
+++ modules/rep_tax_cash_basis/includes/tax_cash_db.inc    Wed May 06 10:49:31 2015
@@ -163,7 +163,7 @@
             0 payable,
             bt.amount*ex_rate gross_input,
             ttd.net_amount*ex_rate net_input,
-            ttd.amount*ex_rate collectible,
+            -1*ttd.amount*ex_rate collectible,
             ttd.rate,
             bt.type,
             bt.person_type_id,
@@ -190,7 +190,7 @@
             0 payable,
             bt.amount*ex_rate gross_input,
             ttd.net_amount*ex_rate net_input,
-            ttd.amount*ex_rate collectible,
+            -1*ttd.amount*ex_rate collectible,
             ttd.rate,
             bt.type,
             bt.person_type_id,

4,094

(0 replies, posted in Reporting)

In order to
1. study the implementation of TCPDF in FA 
2. and attempt to update it to some later version
3. and / or backporting some fixes / functionality
4. without increasing bloat as referred to in a post by @itronics,
I have started a separate GitHub Repo for the same.

It starts with the the raw TCPDF v4.0.027 that is the base version used in FA and then traverses the changes in it thereafter. These commits are certainly there in the official Github repo but not bunched together.

https://github.com/apmuthu/TCPDF_FA

Anyone having the ligatures for Tamil?

1. Why was arialunicid0.php removed from reporting/fonts folder? Does the current cid0XX.php files from the TCPDF project replace them?

2. Any examples of Indic fonts being successfully used for reporting in FA?

3. FreeSans.ttf needs to be added to the reporting/fonts/ folder since it is the default used for unicode in reporting/includes/class.graphic.inc in line 160, now that everything is going unicode... The said font can be taken from the GNU Project Archives.

4. $UTF8_fontfile defined in config.php needs to have the font file (TTF/OTF, etc) in the reporting/fonts/ folder as well but that is an enduser choice of override.

5. Complex Ligatures as in Indic Scripts (Hindi/Devanagri, Tamil, etc) are discussed here for Jasper Reports and developed for PDF Export using the Open Office Library here. Using Java with iText for Indic Scripts is discussed here. Indic Script usage in Jasper Reports using Unicode is discussed here.

@peter: Thanks for the feedback. Often times, users solve their issues but fail to report the solution and others must traverse the same path again....

4,097

(8 replies, posted in Translations)

Attached is the latest full PO that needs the blank strings to bear the translations. Use NotePad++ and choose encoding to be UTF-8 without BOM.

The file is also in my unofficial GitHub repo.

4,098

(8 replies, posted in Translations)

Issue #6 is open in my unofficial GitHub Repo for Tamil Language installation with screenshots.

@mark0300: Thanks. Attached herewith.

4,100

(154 replies, posted in Modules Add-on's)

@peter: please compare your CoA with that of the standard sql/en_US-new.sql for field order differences and correct them to match the latter. Many CoAs are "broken" and some like the en_GB are corrected in my unofficial GitHub Repo.