有這方面需求的人,可以到官網去提一下建議,協助他們把 i18n 加到 Drupal 核心裡。
參考:Looking for internationalization use cases and application feedback
If you have built a site with Drupal or some other system, where internationalization was a requirement, we would welcome a writeup of how did i18n fit into that system, what were the requirements and the desired workflow. We are looking for use cases to build a map of what should we think about when planning the Drupal internationalization subsystem.
不是很建議把I18N放進核心中
個人是認為多國語系的網站管理並不是很常碰到,而且這個議題通常不是技術方面的議題。
目前的I18N模組做的很好,運作也很正常,沒有必要一定要放進核心中,放進去反而會造成核心變大。
老實說,i18n很不成熟.
老實說,i18n很不成熟...
就放到核心的code來說,太嫩了~架構並不好,很多是髒的方式