Back to guides

Lunar New Year Gift Tags: Open a Blessing Message in Your Language

One gift tag can carry a blessing in several languages, because an NDEF message holds one text record per language code. Here is how to write it, order it and test it.

Published

A Lunar New Year gift NFC tag can hold the same blessing in more than one language, because an NDEF message can carry one text record per language code. Write the record your relative reads best first, add the others after it, and test the tag on their kind of phone before you wrap it. Lunar New Year 2027 falls on 6 February, so there is time to get this right.

If you have not made a tag with a message before, start with our guide to NFC gift tags that carry a tap-to-read message. This one covers the part that is specific to families who read different languages: how to put several on one tag, in which order, and how much memory that takes.

How one tag can hold a message in several languages

Every NFC Forum tag stores its data as an NDEF message, whatever its chip type. The NFC Forum describes five tag types that differ in protocol and data layout but behave the same overall, and a phone that reads the message acts on what is stored in it. A message is a list of records, and one record type is the text record.

What a text record holds

A text record has two parts: the text itself and a language identifier such as "en". The Android developer guide shows the structure: the language bytes are written as ASCII, and a status byte records whether the text is UTF-8 or UTF-16 and how long the language code is. For the details of both encodings, see our guide to NDEF text records, UTF-8 and language codes. For a gift tag, use UTF-8. It covers Chinese, Korean, Vietnamese, Japanese and Latin scripts in the same message.

One record per language

The Nordic nRF Connect SDK documentation states the rule plainly: a message can contain only one text record for each language code. That is the feature you want here. A tag can hold a "zh" record, an "en" record and a "vi" record side by side. What it cannot hold is two "en" records. If you have two English greetings, merge them into one record.

Why text and not a link

A link needs a connection and a page that stays online. A text record shows the words directly when the tag is read. For a short blessing in a card or on a gift box, that is simpler and it works with no signal at all. If you want a video or a photo page instead, a link is the right record, and our digital red envelope guide shows that route.

Write the blessing tag in NFCore

You need three things: a writable tag, a phone and the blessing text. NFCore is our app for reading and writing tags on iPhone and Android. It doesn't store anything in the cloud and needs no account.

Plan the wording

Keep each blessing short. One line such as "Happy New Year" in English and "新年快乐" in Chinese is enough, and every extra word costs bytes on the tag. If you are not fluent in a language, ask a relative who is to check your wording before you write it. A blessing with a mistake in it is worse than no translation at all.

Decide the language codes too. Use the standard short codes: "en" for English, "zh" for Chinese, "vi" for Vietnamese, "ko" for Korean, "ja" for Japanese. One code means one record, so the number of languages is the number of records.

Add one text record per language

In the app, open the write screen, add a text record, set the language code, and type the blessing. Repeat for each language. Keep the most important language first (the next section explains why). When the list looks right, hold the phone against the tag until the write finishes.

Read it back

Before you wrap anything, use the read screen to open the tag again. Check three things: every record is there, each one has the language code you meant, and the characters display correctly. A garbled character usually means the text went in with a different encoding than you expected. Rewrite the record rather than guessing.

Record order and what the phone shows

People skip record order. It matters. The Android developer guide says the tag dispatch system looks at the first NDEF record to decide what to do, and it warns not to assume the full payload is in that first record. In practice, most readers and apps treat the first record as the main message.

So put the language your recipient reads best first, and the others after it. If the tag is for a household that shares one language, make that the first record and use the rest as a courtesy.

We can't tell you that a phone will pick the record that matches its system language. We found no source that promises it, so treat it as app-dependent. Some apps show only the first record, some list all of them. The safe approach is to test on the recipient's kind of phone, iPhone or Android, and see what appears.

Pick a tag with enough memory

Text in Chinese, Korean or Japanese takes more bytes per character than English in UTF-8, and every record also carries its own header and language code. Three short blessings usually fit on a small tag, but write them, then check the used and free bytes in the app before you rely on it. If you want room for more languages or a longer note, move up a size. Our guide to NTAG213, NTAG215 and NTAG216 lists the capacities.

Form matters too. A sticker tag fits under a ribbon or inside a card. A card-shaped tag can slip into a red envelope. Avoid putting a tag directly on metal, such as a tin lid, because metal can stop a tag from being read. A paper or card backing between the two helps.

Gift ideas

  • Gift box: a sticker tag under the ribbon, with a small "tap here" mark so the recipient finds it.
  • Card: a tag inside a greeting card, with the blessing in the reader's language first.
  • Grandparent gift: a tag with the first record in the grandparent's language and the second in the grandchildren's, so each side of the family reads their own.
  • Group present: one tag for a shared gift, with a record for each family branch.

Tell the recipient how to read it: unlock the phone and touch it to the tag. If they have never done it, a one-line note on the card saves a phone call. Our first-tap walkthrough for gift recipients covers what to say.

Conclusion

One tag, one text record per language, and the most likely language first. Write the blessing, read it back, test it on the recipient's kind of phone, and only then wrap the gift. The tag is small, but a message that opens in someone's own language is a detail people remember. To start, open NFCore and write the first record.

Frequently Asked Questions

Will the phone show the blessing in my language automatically?

Not something to promise. The tag stores one text record per language code, but which one a phone or app shows depends on the app. Android hands the first record to the dispatch system, so put the most likely language first, and test on the recipient's kind of phone.

Can I put two records with the same language code on one tag?

No. A message can contain only one text record for each language code. Use different codes, such as zh, en and vi, or put the extra text into one longer record.

Do Chinese characters work on an NFC tag?

Yes. A text record can be UTF-8 or UTF-16, and UTF-8 covers Chinese, Korean, Vietnamese and other scripts. Chinese text takes more bytes than English, so check the tag's memory.

Which tag size should I buy for a gift?

A short blessing in two or three languages fits a small tag like NTAG213, but non-Latin text uses more bytes per character. See the size guide and check the byte count before you write.