# Access to \`common.\` data-i18n from custom nodes
**URL:** https://discourse.nodered.org/t/access-to-common-data-i18n-from-custom-nodes/10585
**Category:** Feature Requests
**Created:** [26 April 2019 20:26 UTC](https://discourse.nodered.org/t/access-to-common-data-i18n-from-custom-nodes/10585 "2019-04-26T20:26:49Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@yoiang](https://discourse.nodered.org/u/yoiang)
#### Post date: [26 April 2019 20:26 UTC](https://discourse.nodered.org/t/access-to-common-data-i18n-from-custom-nodes/10585/1 "2019-04-26T20:26:49Z")
Hey y'all!
Since so many of our custom nodes include many of the same configurable values as the core nodes it'd be great to be able to reference `common.*` **data-i18n** translations rather than duplicating and doubly maintaining those translations in our own node's message catalog.
Cheers!
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [26 April 2019 20:32 UTC](https://discourse.nodered.org/t/access-to-common-data-i18n-from-custom-nodes/10585/2 "2019-04-26T20:32:37Z")
Hi, you can already do that by using `node-red:common.blah` as the key.
---
### Author:  [@yoiang](https://discourse.nodered.org/u/yoiang)
#### Post date: [26 April 2019 20:45 UTC](https://discourse.nodered.org/t/access-to-common-data-i18n-from-custom-nodes/10585/3 "2019-04-26T20:45:24Z")
Ah great, thanks so much!
For future visitors of this post it is documented here: [https://github.com/node-red/node-red/wiki/Design:-i18n#internationalization](https://github.com/node-red/node-red/wiki/Design:-i18n#internationalization)
And to see what is available to the Editor in English, for example: [https://github.com/node-red/node-red/blob/master/packages/node\_modules/%40node-red/editor-client/locales/en-US/editor.json](https://github.com/node-red/node-red/blob/master/packages/node_modules/%40node-red/editor-client/locales/en-US/editor.json)