Capitalized type names inside <type>

[alfsb]

On language/types/array.xml the basic type names are capitalized, as common words, even inside <type> tags.

The <type> tag is rendered as a normal text:

I would like to change these few places where capitalized type names occurs, or to remove the surrounding type tag (or to lower the names inside the tags) as PHP types are case sensitive. There are preferences in this case? Remove the tags or to lower, all this cases?

XML source:

doc-en/language/types/array.xml

Line 89 in a0fcdcb

<type>String</type>s containing valid decimal <type>int</type>s, unless the number is preceded by a <literal>+</literal> sign, will be cast to the

[Girgias]

Types are not case-sensitive in PHP: https://3v4l.org/HMEUj

For XML markup, if what we are describing is a type it should be in a type tag. Otherwise, it shouldn't. Regardless of case

The issue with linking/rendering types has been an issue for a while on the PhD side and I do have a PR open for that which I probably should look into again.

[alfsb]

Types are not case-sensitive in PHP: https://3v4l.org/HMEUj

Oh, I will change my validation scripts to reflect that.

The issue with linking/rendering types has been an issue for a while on the PhD side and I do have a PR open for that which I probably should look into again.

I recently fixed an issue on pt_BR where linking on <function> was failing because whitespace inside the tag. So I suggest trim() and strtolower() the tag's content before calculating link targets.

[Girgias]

Types are not case-sensitive in PHP: https://3v4l.org/HMEUj

Oh, I will change my validation scripts to reflect that.

What sort or scripts do you have? We have a scripts/qa folder in doc-base and it could be sensible to run them as part of PRs

[alfsb]

What sort or scripts do you have? We have a scripts/qa folder in doc-base and it could be sensible to run them as part of PRs

Scripts that check if translations are defining the same attributes, entities, tags, on the same files, as the original files. Basically checking for unbalanced XML usage between en/ and translations.

See: https://github.com/alfsb/doc-base/tree/master/scripts/translation#some-useful-scripts-for-maintaining-translation-consistency-of-manual

They are basically QA scripts, but work by comparing two trees. With this I already catch a lot of mistyped or portly translated files on pt_BR, as some inconsistency usage. See, for example, #2664 (en) and php/doc-pt_br@eae2d59 (translation).

I plan to integrate them afterwards, but I'm somewhat blocked by php/doc-base#69, as it implies there is a better licensing option for newer doc scripts.

[Girgias]

I don't know much about licensing, so I've shouted into the void on Mastodon.