Title: localization issue
Last modified: August 21, 2016

---

# localization issue

 *  Resolved [aluizioll](https://wordpress.org/support/users/aluizioll/)
 * (@aluizioll)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/localization-issue-2/)
 * I’m working in the Portuguese translation for the Plug-in and I found a non translatable
   string in views/post_type.php line 564 “Off”.
    Also, I’d like to know how could
   I contribute with this translation like whom to send it.
 * [http://wordpress.org/extend/plugins/custom-content-type-manager/](http://wordpress.org/extend/plugins/custom-content-type-manager/)

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Thread Starter [aluizioll](https://wordpress.org/support/users/aluizioll/)
 * (@aluizioll)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/localization-issue-2/#post-3871154)
 * I’d like to reinforce also that some localization functions like _e() are used
   without the “plugin text domain name”. One could work on some code to parse all
   of the project files in order to check for this issue (I’d do it but my knowledge
   in regex is very bad). An example could be seen in views/metabox.php in the lines
   below 50, in the next _e() functions.
 *  Plugin Contributor [fireproofsocks](https://wordpress.org/support/users/fireproofsocks/)
 * (@fireproofsocks)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/localization-issue-2/#post-3871265)
 * Please direct all this sort of thing to the bug tracker: [http://code.google.com/p/wordpress-custom-content-type-manager/](http://code.google.com/p/wordpress-custom-content-type-manager/)
 * Some strings do not include the plugin text domain when the word or phrase is
   so simple or common that it is in the WP lexicon already. Others I may have missed.
 * Regex’s for this would be prohibitively complex: the entire paradigm that WP 
   relies on has severe limitations because it relies on software (e.g. POEdit) 
   that parses *text* and not PHP.
 *  Thread Starter [aluizioll](https://wordpress.org/support/users/aluizioll/)
 * (@aluizioll)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/localization-issue-2/#post-3871272)
 * Well, regex was just a suggestion for you to parse and replace _e() functions
   with ‘_e+the function argument of text domain’, but as you said this should not
   be an issue as you leave this strings to WP po files. But there are still some
   strings without _e functions so they are not able to be translated. I changed
   the core, but in next updates it will be excluded. I’ll post this in the place
   you asked for.
 *  Plugin Contributor [fireproofsocks](https://wordpress.org/support/users/fireproofsocks/)
 * (@fireproofsocks)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/localization-issue-2/#post-3871273)
 * Thanks. I got the bug report.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘localization issue’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/custom-content-type-manager_c9c790.
   svg)
 * [Custom Content Type Manager](https://wordpress.org/plugins/custom-content-type-manager/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/custom-content-type-manager/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/custom-content-type-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/custom-content-type-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/custom-content-type-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/custom-content-type-manager/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [fireproofsocks](https://wordpress.org/support/users/fireproofsocks/)
 * Last activity: [12 years, 11 months ago](https://wordpress.org/support/topic/localization-issue-2/#post-3871273)
 * Status: resolved