The right way will be to filter the output, and you have a very handy filter just for that called gettext. The second reason is that it is just a bad practice. The reason is that your new translation, if applied with the standard codes ( en_US ) would be overwritten in each update, and also, you will have a hard time maintaining it. This is not the right way to approach the problem. pot file to see if there were any updates to be added too.
PORTUGUESE BRAZILIAN AS POEDIT FILE SUGGEST HOW TO
I have already done so in a very extreme case ( literally with xx_XX ) Updated translations for the brazilian portuguese language made with Poedit 3, i closed the issue related to this now that i learned how to make pull requests.
The official language codes can be found here ( since wordpress is using the gettext utility ) but Like I said, defining a language as xx_XX and then declaring define ('WPLANG', 'xx_XX') will indeed work as expected. So, the Brazilian Portuguese file would be called ptBR.mo, and a non-specific Portuges file would be called pt.mo. pt for Portuguese) followed by the ISO-3166 country code (e.g. The European Central Bank (ECB) is the central bank of the 19 European Union countries which have adopted the euro. See the complete list of language codes and country codes to find your exact locale. So, the Brazilian Portuguese file would be called ptBR.mo.
pt for Portuguese) followed by the country code (e.g.
xx_XX ) will work, and you can invent your own. mo files is based on the ISO-639 language code (e.g. The naming convention is based on the language code (e.g. To directly answer your question : any name ( e.g.
0 kommentar(er)
