Mailing List Archive: Re: svn commit: r1880368 - /httpd/httpd/trunk/docs/manual/style/lang-targets.xml

Re: svn commit: r1880368 - /httpd/httpd/trunk/docs/manual/style/lang-targets.xml

Aug 19, 2020, 7:35 AM

Post #1 of 5 (770 views)

On Wed, Aug 19, 2020 at 10:08:12AM +0200, Christophe JAILLET wrote:
> Le 19/08/2020 à 09:47, Joe Orton a écrit :
> > Stupid question, why do we need to change the suffix to .utf8 to convert
> > these files into UTF-8?
>
> I don't think it is needed, just a matter of consistancy in naming.
> See r1878788 to see the magic needed to concert to UTF-8 (without renaming
> files)

[Adding docs@ to CC.]

Shall we move everything (except for Korean?) to UTF-8 and drop the
.utf8 suffix as well? It would still be consistent then.

(I only just renamed those files but, revisions are cheap? ;)

Only problem is the 100-part SVN commit diff e-mail?

Regards, Joe

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org

Re: svn commit: r1880368 - /httpd/httpd/trunk/docs/manual/style/lang-targets.xml [ In reply to ]

wrowe at rowe-clan

Aug 19, 2020, 7:49 AM

Post #2 of 5 (770 views)

Permalink

On Wed, Aug 19, 2020 at 9:35 AM Joe Orton <jorton@redhat.com> wrote:

> On Wed, Aug 19, 2020 at 10:08:12AM +0200, Christophe JAILLET wrote:
> > Le 19/08/2020 à 09:47, Joe Orton a écrit :
> > > Stupid question, why do we need to change the suffix to .utf8 to
> convert
> > > these files into UTF-8?
> >
> > I don't think it is needed, just a matter of consistancy in naming.
> > See r1878788 to see the magic needed to concert to UTF-8 (without
> renaming
> > files)
>
> [Adding docs@ to CC.]
>
> Shall we move everything (except for Korean?) to UTF-8 and drop the
> .utf8 suffix as well? It would still be consistent then.

Why not Korean? It maps very well to utf-8, similar to Japanese it has a
basic
phonetic alphabet, but borrows a significant number of Han (Hangul in
Koreans)
characters from the CJK set.

Re: svn commit: r1880368 - /httpd/httpd/trunk/docs/manual/style/lang-targets.xml [ In reply to ]

mrumph68 at gmail

Aug 19, 2020, 7:50 AM

Post #3 of 5 (770 views)

Permalink

Would it be possible to skip the SVN commit diff email?
Like it is possible with [skip ci] to bypass the CI runs.

On Wed, Aug 19, 2020 at 7:35 AM Joe Orton <jorton@redhat.com> wrote:

> On Wed, Aug 19, 2020 at 10:08:12AM +0200, Christophe JAILLET wrote:
> > Le 19/08/2020 à 09:47, Joe Orton a écrit :
> > > Stupid question, why do we need to change the suffix to .utf8 to
> convert
> > > these files into UTF-8?
> >
> > I don't think it is needed, just a matter of consistancy in naming.
> > See r1878788 to see the magic needed to concert to UTF-8 (without
> renaming
> > files)
>
> [Adding docs@ to CC.]
>
> Shall we move everything (except for Korean?) to UTF-8 and drop the
> .utf8 suffix as well? It would still be consistent then.
>
> (I only just renamed those files but, revisions are cheap? ;)
>
> Only problem is the 100-part SVN commit diff e-mail?
>
> Regards, Joe
>
>

Re: svn commit: r1880368 - /httpd/httpd/trunk/docs/manual/style/lang-targets.xml [ In reply to ]

jorton at redhat

Aug 20, 2020, 7:21 AM

Post #4 of 5 (765 views)

Permalink

On Wed, Aug 19, 2020 at 09:49:21AM -0500, William A Rowe Jr wrote:
> On Wed, Aug 19, 2020 at 9:35 AM Joe Orton <jorton@redhat.com> wrote:
>
> > On Wed, Aug 19, 2020 at 10:08:12AM +0200, Christophe JAILLET wrote:
> > > Le 19/08/2020 à 09:47, Joe Orton a écrit :
> > > > Stupid question, why do we need to change the suffix to .utf8 to
> > convert
> > > > these files into UTF-8?
> > >
> > > I don't think it is needed, just a matter of consistancy in naming.
> > > See r1878788 to see the magic needed to concert to UTF-8 (without
> > renaming
> > > files)
> >
> > [Adding docs@ to CC.]
> >
> > Shall we move everything (except for Korean?) to UTF-8 and drop the
> > .utf8 suffix as well? It would still be consistent then.
>
> Why not Korean? It maps very well to utf-8, similar to Japanese it has
> a basic phonetic alphabet, but borrows a significant number of Han
> (Hangul in Koreans) characters from the CJK set.

Only because I do know that ISO-8859-1 (which all the other non-UTF-8
sources use) does map trivially to UTF-8 but have no idea about EUC-KR.
So, if there's no reason why we can't do them all, let's do them all.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org

Re: svn commit: r1880368 - /httpd/httpd/trunk/docs/manual/style/lang-targets.xml [ In reply to ]

nilgun at belgeler

Aug 22, 2020, 1:18 AM

Post #5 of 5 (758 views)

Permalink

Hi,

The tr suffix is a MIME-type for application/x-troff.
Therefore, httpd cannot access Turkish pages.
The tr.utf8 suffix solves this problem, and utf8 suffix is unnecessary
for other languages.

Regards, Nilgün

Joe Orton <jorton@redhat.com>, 20 A?u 2020 Per, 17:21 tarihinde ?unu yazd?:
>
> On Wed, Aug 19, 2020 at 09:49:21AM -0500, William A Rowe Jr wrote:
> > On Wed, Aug 19, 2020 at 9:35 AM Joe Orton <jorton@redhat.com> wrote:
> >
> > > On Wed, Aug 19, 2020 at 10:08:12AM +0200, Christophe JAILLET wrote:
> > > > Le 19/08/2020 à 09:47, Joe Orton a écrit :
> > > > > Stupid question, why do we need to change the suffix to .utf8 to
> > > convert
> > > > > these files into UTF-8?
> > > >
> > > > I don't think it is needed, just a matter of consistancy in naming.
> > > > See r1878788 to see the magic needed to concert to UTF-8 (without
> > > renaming
> > > > files)
> > >
> > > [Adding docs@ to CC.]
> > >
> > > Shall we move everything (except for Korean?) to UTF-8 and drop the
> > > .utf8 suffix as well? It would still be consistent then.
> >
> > Why not Korean? It maps very well to utf-8, similar to Japanese it has
> > a basic phonetic alphabet, but borrows a significant number of Han
> > (Hangul in Koreans) characters from the CJK set.
>
> Only because I do know that ISO-8859-1 (which all the other non-UTF-8
> sources use) does map trivially to UTF-8 but have no idea about EUC-KR.
> So, if there's no reason why we can't do them all, let's do them all.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
> For additional commands, e-mail: docs-help@httpd.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org