|
Hy fellows,
we're working hard for getting as much ready as we
can for the proposed release 0.7 of our Zend Framework. I hope you enjoy
reading our progress and give us good feedback.
4th NEWSLETTER for the I18N
TEAM
WEEKLY SUMMARY:
Some new source integrations for Zend_Translate were proposed
Zend_Translate_Array - useage of simple PHP arrays for translation
Zend_Translate_Csv - useage of csv seperated files for translation
Zend_Translate_Qt - useage of Qt linguist files for translation
Zend_Translate_Tbx - useage of Termbase Exchange Link files for
translation
Zend_Translate_Xliff - useage of XLIFF xml files for translation
Zend_Translate_XmlTm - useage of XML:TM namespace xml files for
translation
For Zend_Date's get(), add() and sub() functions were new
formats added. Now language localized date and time inputs are recognised. A
compare() function was implented for all formats and cloneIt().
For Zend_Locale_Format some issues were fixed which have been found by unit
tests.
The new proposed class Zend_Timesync adds the ability for syncronising to
external timeservers to the framework.
Supported formats will be NTP, SNTP and SWATCH. We hope that this proposal
makes it through the proposal process. Take a look at http://framework.zend.com/wiki/display/ZFPROP/Zend_TimeSync+-+Thomas+Weidner
Some days ago a discussion raised in our community chat on the useage of
UTF8. We found out that within the proposal process for Zend_Locale we spoke
about the useage of mbstring but we forgot about iconv.
By useage of iconv we could erase the need of the Zend_Locale_UTF8
class.
Improvement would be the useage of php internal functions which means
speed.
Contra would be that iconv needs to be added to the minimum
requirements.
Gavin is looking forward if we could add iconv to the ZF
requirements.
Until a official statement was given, the coding of Zend_Locale_Format is
freezed.
We will force the completion of Zend_Date until then.
Another interesting discussion was raised by André about the possible
conversion of for example arabic or indian numbers to international numbers. We
would include this ability in our already existing number conversion class
Zend_Measure_Number, by using Zend_Locale_UTF8, which already can convert
between different formats as roman numbers, hexadecimal numbers and so on. When
needed, we could then define that numbers within Zend_Locale_Format should be
automaticaly converted from arabic to international and visaversa, or we could
add this by using a new parameter.
ACTUAL PROGRESS:
Within the Locale team the following classes will
be developed...
Class - percent done
------------------------------
Zend_Locale - 75%
Zend_Date - 55%
Zend_Calendar -
0%
Zend_Measure - 100%
Zend_Currency - 0%
Zend_Translation - 0%
Zend_Timesync - 0%
DETAILS per CLASS:
Zend_Locale:
Implementation in progress.
Zend_Locale_Data:
Implementation complete - Internal
class.
Zend_Locale_Format:
Implementation in progress (for Date and Time and
also for UTF8 useage).
Zend_Locale_UTF8:
Implementation on hold (by André) - Internal
class
Zend_Translate:
Actually on hold, proposal written
Zend_Translate_Abstract:
actually on hold
Zend_Translate_Gettext:
actually on hold
Zend_Translate_TMX:
actually on hold
Zend_Translate_SQL:
actually on hold
Zend_Translate_Array:
actually on hold
Zend_Translate_Qt:
actually on hold
Zend_Translate_TBX:
actually on hold Zend_Translate_CSV:
actually on hold
Zend_Translate_Xliff:
actually on hold Zend_Translate_XMLTM:
actually on hold Zend_Date:
Implementation in progress
Zend_Calendar:
actually on hold.
Zend_Currency:
actually on hold.
Zend_Timesync:
actually on hold.
Implementation completed
Summary:
We hope you stay with us, and maybe the one or other helps us within the
team. |
