Phreesoft Support Forum

Dave,

I sent you the beta version of sp_cri translation for Phreebooks1.8 for your review and testing.

The only thing missing is the translation of the Help files.

Included are the translated COA, STD reports with freeserif fonts and translation for the add-on modules: Assets, Rma, ZenCart and Translator. For these add-on modules, the language of the extra_menus is hard-coded and will not change with login language setting.

The English GPL License is hard-coded in the install module. A Spanish translation, licencia.htm is included.

There are two big issues that I have come across so far, and I think they are code related and are:

1. The translated files are not being pulled in the Company menu choices.
2. The install module help pop-ups also bring up the English text instead of the translation.

These are some more items of the to do list for sp_cri:

Fully test and tune the language terms.

Move remaining hard-coded English language items to the language files.

Change meta references in help *.htm files from ISO 8859-1 to utf-8 to display correct language characters.

Change the referencing system of PhreeHelp contents to be able to see all help files (and not only the index page as happens now) when connecting to the server via ssh with port forwarding.

Add missing links in help files to the existing English files (Demo site also) For example: User Manual->Customers->Customers Home.

Add reports for freesans fonts which are closer in appearance to the default helvetica used for the English version.

In the code, change mysql calls utf8_unicode_ci to utf8_general_ci as in Spanish the simplified sorting gives the same results and is faster.

Translate the demo data.

Ruben.

_________________
Ruben.

Got them, thanks. I will take a look and if I don't find anything big, I'll post them for others. to view. This would also be a good opportunity to try the new translator module to see if you missed any files. It is available on the website.

Dave

Hi.
I have seen the spanish translation at the demo.
How can I get that?

Thanks very much.

The files for R1.8 can be downloaded from the downloads section of www.phreebooks.com

In a few days I'll have ready the files for R2.0.

_________________
Ruben.

Thanks very much!

I again.
Can I help you in translation??
Let me know...

Just posted Spanish translation for Release 2.0 from rulola. It can be found in the Downloads section under translations.
Dave

I will try it.
Thanks very much.

Thanks for offering to help with the spanish translation.

Still pending are some reports and most of the help files.

Help files
--------------
Only a few files have been translated. You can find the latest translated files in es_cr_R2.0_20100325.zip which is posted in the downloads section on the website.
They are in html. I suggest you start with Chapter 7.

Reports
------------
The new reports or updated reports after R1.8 need to be translated.

The translation is a two part process as follows.
1. Open the report with a text editor and translate the field descriptions up to the line that states DO NOT EDIT BELOW THIS LINE.
2. Upload the report to a server that has Phreebooks installed and translate the fields in the Field Setup Screen of the report editor

I suggest you begin with the list of reports that follows. Get the original english version from release R2.0, my_files/reports

AccountReconciliation.rpt.txt
AgedPayablesSummary.rpt.txt
AgedReceivablesSummary.rpt.txt
BalanceSheetwtihSubaccounts.rpt.txt
CustomerPaymentMethods.rpt.txt
DailyCashReport.rpt.txt
DailyRegister.rpt.txt
IncomeStatementw_Budget.rpt.txt
IncomeStatmntwithSubaccount.rpt.txt
InventoryValuation-Branch.rpt.txt
NegativeInventoryBalances.rpt.txt
OpenSObyItem.rpt.txt
PurchaseOrderwithShipping.rpt.txt
SalesByRep.rpt.txt
SalesBySKU.rpt.txt

_________________
Ruben.

Looking for Spanish translation files for 3.0

Anybody out there working on this?

_________________
Alvin

If you want to help, I can give you a start based on the 2.1 translation. It will need to be reviewed and some new lines added. It can all be done with the translator module. Let me know.

Dave

Whatever you can give me will help. I grabbed a copy of the translator module the other day, but have not found time to load it...

thanks for the help

Alvin

_________________
Alvin

I converted a 2.1 translation over and included it here. I also improved the translator module and added it here as well. Will post it on the website soon. Read the readme.txt file for help getting started.

Dave

OK did this:
Installation Procedure:
1. unzip and upload to the module directory.
2. Go to Company -> Module Admin -> click install.

The first step is to upload an older release of the language to
translate to (i.e. fr_fr for release 2.1).

1. Click on the Upload icon and enter the language to create (i.e.
fr_fr), enter All for all modules (this is necessary since the
modules from 2.1 don't align with 3.0), enter the release number
(2.1 since its an older version), Select a zipped language file to
upload. The file will be uploaded and all 'defines' will be
extracted into the db.
But I see no Upload button, the action column only has Remove button.

What do you think? OK what I needed to do was set access in Company -> Users, logout login then go to Tools -> Translator Assistant...

_________________
Alvin

Go to user setup and allow full access to the translator module. Log out and back n and you will see the Translator Assistant in the Tools menu.

1. Upload the file (zipped) and set as Language: es_cr, Modules: All, Version 2.1. This will upload, unpack and set the default cosntants.

2. Import the current install language from the current install, en_us.

3. Create a new language es_es, create from en_us and check the box to overwrite, set the language to es_cr (same as step 1) and module to all. This will create about 40-50 new files.

4. You can edit each one individually, select the translated box after each is translated and save when completed. You can also export all to create the new translation output.

Dave