A few more same that could be updated as well
https://curl.haxx.se/libcurl/c/curl_share_strerror.html
https://curl.haxx.se/libcurl/c/curl_multi_strerror.html

I usually go with "zero" in text instead of "nul" only because "nul" is too close to "null" and they're pronounced the same way and it certainly isn't NULL terminated...

I usually go with "zero" in text instead of "nul" only because "nul" is too close to "null" and they're pronounced the same way and it certainly isn't NULL terminated...

Fair enough. I think there are lots of different opinions, although not seen 'zero' before. BSD generally call it 'NUL'. ASCII and https://en.wikipedia.org/wiki/ISO/IEC_646 call it NUL

POSIX strcpy()
http://pubs.opengroup.org/onlinepubs/9699919799/functions/strcpy.html

glibc:
https://www.gnu.org/software/libc/manual/html_node/Converting-Strings.html

The C and C++ standards don't use "zero".

I had a look at the linux man pages, they're consistently describing as "including the terminating null byte ('\0')"

https://man7.org/linux/man-pages/man3/strcpy.3.html

Cheers

My strcpy man page on Debian even uses the phrase "null-terminated".

"man ascii" describes the character as NUL '\0' (null character)

I put up a very unscientific poll on twitter about it:

https://twitter.com/bagder/status/1276074546530000896

Hi! null-terminated is the in common use. Personally I use NUL terminated, as it's clear it's not a NULL ptr, although C++ now has the nullptr keyword.

I looked online quite a few in favour of NUL

https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
GCC uses NUL "-Wno-format-contains-nul
If -Wformat is specified, do not warn about format strings that contain NUL bytes."

http://man7.org/linux/man-pages/man7/bpf-helpers.7.html

int bpf_probe_read_str(void *dst, int size, const void *unsafe_ptr)

          Description
                 Copy a NUL terminated string

POSIX uses NUL
http://man7.org/linux/man-pages/man3/strncpy.3p.html
" If a NUL character is written to the destination, the stpncpy()
function shall return the address of the first such NUL character."

http://man7.org/linux/man-pages/man3/strchr.3.html

strchrnul()
It's even called NUL in the function name

C11 Annex K uses NUL
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1969.htm

If we are going to change this phrase, we should go with the common, most preferred one, or not change it at all. Then it is really not a question of which our own personal preferences are...

Also, the question is not what the character or byte is called. The question is how to say zero terminated the most common/standard way.

Right. The funny thing is I typically only hear the phrase "null-terminated", so no idea how people would write it. I don't recall ever hearing "zero-terminated" (in context of strings) even though it's perfectly understandable.
As a side note: in C++ this is simply called a "c-string" :)

C++ ISO/IEC
14882 uses "null-terminated"

C ISO/IEC
9899 uses "null character"

"7.1.1 Definitions of terms
1 A string is a contiguous sequence of characters terminated by and including the first null
character. The term multibyte string is sometimes used instead to emphasize special
processing given to multibyte characters contained in the string or to avoid confusion
with a wide string. A pointer to a string is a pointer to its initial (lowest addressed)
character. The length of a string is the number of bytes preceding the null character and
the value of a string is the sequence of the values of the contained characters, in order."

C++ ISO/IEC
14882 uses "null-terminated"

I meant "cstring" is used in commonly by C++ programmers (most probably because it's short ;) ).
In any case "null-terminated" seems to be the most common of calling it, so #5608 is the way to go.

uses "null character

Finish this sentence: "A C string is a sequence of bytes that is..."

1. "null-terminated"
2. "null character"

I'm not a native English speaker but I know we can't use (2)...

I'm not a native English speaker but I know we can't use (2)...

And nobody's gonna write / wants to read "terminated by a null character".

I argue that "the string is terminated by a null character" and "the string is null-terminated" are just two sides of the same coin. In both cases we refer to the trailing character using the name "null".

uses "null character

Finish this sentence: "A C string is a sequence of bytes that is..."

1. "null-terminated"
2. "null character"

I'm not a native English speaker but I know we can't use (2)...

Ok, yes I'm a native English speaker:

"A C string is a sequence of bytes which is null-terminated"

I argue that "the string is terminated by a null character" and "the string is null-terminated" are just two sides of the same coin. In both cases we refer to the trailing character using the name "null".

yes, the NUL byte http://www.asciitable.com/ is described as "null".

...Same as LF byte is described as "line feed". For me it seems we either state the macro name, or we provide the description. It's a bit like writing "EINVAL" or "Invalid argument" in relation to errno codes. Or "SIGSEGV" vs "Segmentation Violation" etc.

I don't follow you. What exactly are you proposing?

You submit an issue saying we don't use the common terminology. We dig up the most commonly used and the most commonly preferred terminology but now that's not what you think we should use?

As you say, the mostly commonly used is "null-terminated"

So to give your example, that would be:
"A C string is a sequence of bytes which is null-terminated"