mirror/perl
1
0
Fork 0
mirror of https://github.com/Perl/perl5.git synced 2026-01-27 01:44:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

pod: fix capitalisation of GitHub and other proper nouns

Browse Source
This commit is contained in:
vaitkus 2024-09-04 19:30:29 +03:00 committed by Karl Williamson
parent 27866a3ef2
commit ef6530c500
10 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pod/perl5122delta.pod
View File

@ -231,7 +231,7 @@ stack for their return values in cases where no argument was passed in.
=item *
When matching unicode strings under some conditions inappropriate backtracking would
When matching Unicode strings under some conditions inappropriate backtracking would
result in a C<Malformed UTF-8 character (fatal)> error. This should no longer occur.
See L<[GH #10434]|https://github.com/Perl/perl5/issues/10434>

2
pod/perl5280delta.pod
View File

@ -1711,7 +1711,7 @@ applicable.
=item *
Perl now includes a default F<.travis.yml> file for Travis CI testing
on github mirrors.
on GitHub mirrors.
L<[GH #14558]|https://github.com/Perl/perl5/issues/14558>
=item *

2
pod/perl5320delta.pod
View File

@ -1661,7 +1661,7 @@ floating point number. L<[GH #17062]|https://github.com/Perl/perl5/issues/17062>
=item *
Matching a non-C<SVf_UTF8> string against a regular expression
containing unicode literals could leak a SV on each match attempt.
containing Unicode literals could leak a SV on each match attempt.
L<[GH #17140]|https://github.com/Perl/perl5/issues/17140>
=item *

4
pod/perl5380delta.pod
View File

@ -1367,11 +1367,11 @@ output double quoted strings with various characters escaped so as to
make the exact value clear to a reader. The exact rules on which
characters are escaped may change over time but currently are that
printable ASCII codepoints, with the exception of C<"> and C<\>, and
unicode word characters whose codepoint is over 255 are output raw, and
Unicode word characters whose codepoint is over 255 are output raw, and
any other symbols are escaped much as Data::Dumper might escape them,
using C<\n> for newline and C<\"> for double quotes, etc. Codepoints in
the range 128-255 are always escaped as they can cause trouble on
unicode terminals when output raw.
Unicode terminals when output raw.
In older versions of perl the one liner

4
pod/perl56delta.pod
View File

@ -77,7 +77,7 @@ will be needed to complete the toolkit for dealing with Unicode.
The new C<\N> escape interpolates named characters within strings.
For example, C<"Hi! \N{WHITE SMILING FACE}"> evaluates to a string
with a unicode smiley face at the end.
with a Unicode smiley face at the end.
=head2 "our" declarations
@ -92,7 +92,7 @@ variables. See L<perlfunc/our>.
Literals of the form C<v1.2.3.4> are now parsed as a string composed
of characters with the specified ordinals. This is an alternative, more
readable way to construct (possibly unicode) strings instead of
readable way to construct (possibly Unicode) strings instead of
interpolating characters, as in C<"\x{1}\x{2}\x{3}\x{4}">. The leading
C<v> may be omitted if there are more than two ordinals, so C<1.2.3> is
parsed the same as C<v1.2.3>.

4
pod/perldeprecation.pod
View File

@ -18,7 +18,7 @@ which they will be removed.
=head3 Unicode Delimiter Will be Paired
Some unicode delimiters used to be allowed as single characters, but
Some Unicode delimiters used to be allowed as single characters, but
in the future will be part of a balanced pair. This deprecation category
is used to mark the ones that will change from being unpaired to paired.
@ -37,7 +37,7 @@ Category: "deprecated::dot_in_inc"
=head3 Unicode Property Name
Various types of unicode property name will generate deprecated warnings
Various types of Unicode property name will generate deprecated warnings
when used in a regex pattern. For instance surrogate characters will result
in deprecation warnings.

2
pod/perlebcdic.pod
View File

@ -105,7 +105,7 @@ Portuguese, Spanish, and Swedish. Dutch is covered albeit without
the ij ligature. French is covered too but without the oe ligature.
German can use ISO 8859-1 but must do so without German-style
quotation marks. This set is based on Western European extensions
to ASCII and is commonly encountered in world wide web work.
to ASCII and is commonly encountered in World Wide Web work.
In IBM character code set identification terminology, ISO 8859-1 is
also known as CCSID 819 (or sometimes 0819 or even 00819).

8
pod/perlgit.pod
View File

@ -553,14 +553,14 @@ to push your changes back with the C<camel> remote:
The C<fetch> command just updates the C<camel> refs, as the objects
themselves should have been fetched when pulling from C<origin>.
=head2 Working with Github pull requests
=head2 Working with GitHub pull requests
Pull requests typically originate from outside of the C<Perl/perl.git>
repository, so if you want to test or work with it locally a vanilla
C<git fetch> from the C<Perl/perl5.git> repository won't fetch it.
However Github does provide a mechanism to fetch a pull request to a
local branch. They are available on Github remotes under C<pull/>, so
However GitHub does provide a mechanism to fetch a pull request to a
local branch. They are available on GitHub remotes under C<pull/>, so
you can use C<< git fetch pull/I<PRID>/head:I<localname> >> to make a
local copy. eg. to fetch pull request 9999 to the local branch
C<local-branch-name> run:
@ -580,7 +580,7 @@ which rebases C<local-branch-name> on C<blead>, and checks it out.
Alternatively you can configure the remote to fetch all pull requests
as remote-tracking branches. To do this edit the remote in
F<.git/config>, for example if your github remote is C<origin> you'd
F<.git/config>, for example if your GitHub remote is C<origin> you'd
have:
[remote "origin"]

2
pod/perlhacktips.pod
View File

@ -1825,7 +1825,7 @@ will need to build perl with C<CFG=Debug> or C<CFG=DebugSymbols>.
The Visual Studio profiler is a sampling profiler.
See L<the visual studio
See L<the Visual Studio
documentation|https://github.com/MicrosoftDocs/visualstudio-docs/blob/main/docs/profiling/beginners-guide-to-performance-profiling.md>
to get started.

2
pod/perlre.pod
View File

@ -2667,7 +2667,7 @@ could be all Cyrillic (except for the dot), or they could be a mixture
of the two. In the case of an internet address the C<.com> would be in
Latin, And any Cyrillic ones would cause it to be a mixture, not a
script run. Someone clicking on such a link would not be directed to
the real Paypal website, but an attacker would craft a look-alike one to
the real PayPal website, but an attacker would craft a look-alike one to
attempt to gather sensitive information from the person.
Starting in Perl 5.28, it is now easy to detect strings that aren't