tld_check_8z(3)
β¨ tld_check_8z β¨
okay bestie, welcome to tld_check_8z(3) from the libidn girlies π this is an API function and she is literally the vibe check for your domain name characters. let's get into it π¦
πΈ NAME πΈ
tld_check_8z β API function. that's it, that's the name, she's serving function energy π
β¨ SYNOPSIS β¨
#include <tld.h>
int tld_check_8z(const char * in, size_t * errpos, const Tld_table **
overrides);
yes the line break in the middle of overrides is real, we don't question the ancestors π«Ά
π ARGUMENTS π
const char * inβ a zero-terminated UTF8 string to process. that's the string you're putting on blast, bestie.size_t * errposβ the position of the offending character gets returned right here. she's the receipts πconst Tld_table ** overridesβ aTld_tablearray of extra domain restriction structures that complement and supersede the built-in info. like, they show up AND they outrank. main character behavior fr fr π
π DESCRIPTION π
so what does she actually do? she tests each of the characters in in and checks whether they're allowed by the info in overrides or by the built-in TLD restriction data. vibe check complete β
the rules of the group chat:
- when data for the same TLD is available both internally and in
overrides, the info inoverridestakes precedence. periodt. - if several entries for a specific TLD are found, the first one is used. first come first served, no cap.
- if
overridesisNULL, only the built-in information is used. she's solo dolo π§
the position of the first offending character gets returned in errpos. and hear me on this one bestie:
β οΈ note that the error position refers to the decoded character offset, not the byte position in the string. do not come for me with byte math, it's giving wrong answer π
Return value: she returns the Tld_rc value TLD_SUCCESS if all characters are valid or when tld is null (slay), TLD_INVALID if a character is not allowed (not slay), or additional error codes on general failure conditions (also not slay, sorry babe π).
π REPORTING BUGS π
found a bug? don't suffer in silence, tell the devs:
- report bugs to
<help-libidn@gnu.org>π - general guidelines for reporting bugs:
https://www.gnu.org/gethelp/ - GNU Libidn home page:
https://www.gnu.org/software/libidn/
π COPYRIGHT π
Copyright Β© 2002-2026 Simon Josefsson.
Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. generous queen behavior honestly π
π¦ SEE ALSO π¦
the full documentation for libidn is maintained as a Texinfo manual. if the info and libidn programs are properly installed at your site, this command
info libidn
should give you access to the complete manual. as an alternative you may obtain the manual from:
https://www.gnu.org/software/libidn/manual/
and that's the whole page bestie!! π this was libidn version 1.44, page tld_check_8z(3), and she ate, no crumbs. go validate those characters, ily, bye π«Άβ¨πΈ
π¦ where this page comes from
- arch rolling: libidn 1.44-1 Β· GPL3 AND LGPL
- epel 10: libidn-devel 1.44-1.el10_3 Β· (LGPL-3.0-or-later OR GPL-2.0-or-later) AND GPL-3.0-or-later AND GFDL-1.3-or-later
- fedora 43: libidn-devel 1.44-1.fc43 Β· (LGPL-3.0-or-later OR GPL-2.0-or-later) AND GPL-3.0-or-later AND GFDL-1.3-or-later
- fedora 43: libidn-devel 1.44-1.fc43 Β· (LGPL-3.0-or-later OR GPL-2.0-or-later) AND GPL-3.0-or-later AND GFDL-1.3-or-later
- fedora 44: libidn-devel 1.44-1.fc44 Β· (LGPL-3.0-or-later OR GPL-2.0-or-later) AND GPL-3.0-or-later AND GFDL-1.3-or-later
- fedora 44: libidn-devel 1.44-1.fc44 Β· (LGPL-3.0-or-later OR GPL-2.0-or-later) AND GPL-3.0-or-later AND GFDL-1.3-or-later
- ubuntu stonking: libidn-dev 1.44-1 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms