[wp-trac] [WordPress Trac] #17268: Use native gettext library when available

[WordPress Trac]

#17268: Use native gettext library when available
-------------------------------------------+-----------------------------
 Reporter:  linushoppe                     |       Owner:
     Type:  enhancement                    |      Status:  new
 Priority:  normal                         |   Milestone:  Future Release
Component:  I18N                           |     Version:
 Severity:  normal                         |  Resolution:
 Keywords:  early has-patch needs-refresh  |     Focuses:  performance
-------------------------------------------+-----------------------------

Comment (by ottok):

 MessageFormat is a completely new format. Migration to it would require to
 rewrite current i18n tools, Polyglot, po-editors etc. I strongly advice
 against doing drastic changes here.

 The whole issue here is about low-hanging fruit that has been pending for
 core devs attention for some years.

 I suggest you simply adopt the usage of native gettext when available, and
 then benefit from all optimizations native gettext provides. I agree that
 upstream gettext isn't that actively maintained (having a patch of mine
 waiting for review already over a year..) and maybe PHP gettext isn't the
 latest and coolest either, but they are at least mature and the whole
 ecosystem around .po/.mo file handling works well.

 There is even a patch attached to this issue already. Don't expand the
 scope here, please. Just take in usage gettext as an improvement to the
 current situation and close this issue.

 Optimizations in step 2 and 3 can be tracked in other issues.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/17268#comment:81>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform