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

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

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

William A Rowe Jr
On Wed, Aug 19, 2020 at 9:35 AM Joe Orton <[hidden email]> 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.

Reply | Threaded
Open this post in threaded view
|

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

Joe Orton
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 <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

Nilgün Belma Bugüner
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 <[hidden email]>, 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 <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]