I will put everyone agrees
Quote:
But i think it is better to define that _RTL in xoops and then remove Frameworks/tcpdf/config/lang/*.php
The idea is attractive but TCPDF is natively designed for UTF-8. All these files are in UTF-8. TCPDF manages and displays the ISO charset automatically.
Global.php file can be in UTF-8 but also by ISO. The fact inject ISO files in the configuration of TCPDF disturbs the automatic detection and causes display bugs (we return to the original problem)
Quote:
Also one thing that i forgot.
It can not read the [en] [/en] and [fa] [/fa] codes.
I mean when the website is english it just should makepdf from english content and vice verse.
this is a problem that I noticed. TCPDF does not detect the change of language natively. I plan to add this feature in the next version of tcpdf_for_xoops.
Quote:
Black_beard, whatever you choose, I hope that it will reflect the structure of TCPDF files, i.e. if the next version of TCPDF comes out, we only need to copy the selected files to the /Frameworks/tcpdf directory, and we are done, i.e. we don't have to make any changes to any files, and we don't have to change directories.
Compared to the original version of TCPDF, I modified some files to fit Xoops.
- Files in the directory. / Tcpdf / config / lang / have been renamed. This poses no problem, they are rarely changed.
- I have lightened the class files, history of weight divided by 2 (by some 3). One can easily recover the original files but they are bigger Lots.
- The file "tcpdf_config.php" is the only one where it will make adaptation (but it is rarely changed)
Optimization is my priority. The choices I made in adapting the code I was allowed to reduce memory consumption by 56% and reduce execution time by 36% (baseline version VS version 1.03 of tcpdf_for_xoops)
Quote:
My guide to use _RTL =true/false can help to have less conflicts with newer versions of TCPDF.
It is perhaps for Xoops. But increases the risk of conflict between ISO and UTF-8 (see above) in Tcpdf_for_xoops
Quote:
but only about the directory structure and ease of updates in the future!
The company that I lead will just follow up and updates of these frameworks (I use it for my clients).
I'm busy has put online wiki (french / english) to make best use tcpdf_for_xoops (see
here, the site is still in draft form).
Quote:
A good example is TinyMCE: I can just copy the files except the src. files and I am ready to go. I hope, we can achieve the same with TCPDF, i.e. we can just copy over the files from a new TCPDF release without the need to modify any files on XOOPS.
This is my vision of labor.
The hours of work cost a very expensive
Quote:
no need for them and it makes the work more cleaner. we can read them from xoops!
I'll repeat myself. Xoops is written in iso or utf-8. The day will be 100% Xoops utf-8, we can remove some lines of code. Meanwhile, we must ensure coexistence between utf-8 and iso.*/