Hi, Joe and all,

> The file in question, wsjtx-1.4.0-rc5.log, is *not* a troff file.

Yes!  I fully agree with you!

The server should join our agreement.  At this point, the server
still claims, to any browser fetching the file, it's serving
application/x-troff-man.  That is a server misconfiguration problem.

(For the record: The server claims it's a 2.2.15 Apache on Red Hat.)

I recommend trying to add a file ".htaccess" to the directory that
serves http://physics.princeton.edu/pulsar/K1JT , with the two lines

AddType text/plain .log
AddCharset UTF-8 .log

If that Apache happens to be configured to accept this per-directory
.htaccess configuration (some are, some are not), that will cure the
problem.

Background information on this configuration is available at

http://httpd.apache.org/docs/2.2/en/mod/mod_mime.html#addtype
http://httpd.apache.org/docs/2.2/en/mod/mod_mime.html#addcharset
http://httpd.apache.org/docs/2.2/en/configuring.html#htaccess



> There's no need for and special UTF-8, etc., handling.  If you find a
> few non-ascii characters in the file, you may safely ignore them.

To tell people "this file has problems that you please ignore" is one
way to deal with this.  I think it's better to fix the problem.  Tell
the browsers, not the people.

For that, simply remove the spurious "±" and use UTF-8.



For what it's worth, my own present experience when I open
http://physics.princeton.edu/pulsar/K1JT/wsjtx-1.4.0-rc5.log in my
browser is this:

* As the server tells the browser "this is troff", my browser does
  not know it could simply display the file itself, but instead, opens
  a pop-up "what to do with this file?".

* I choose to open the file with the "gedit" text editor.

* "gedit" complains loudly the file contains invalid characters.  It
  is not certain which encoding to use.  It suggests UTF-8 (the
  correct choice if it were not for the "±"), but warns me that
  content might be lost opening the file that way.

Regards,

Andreas, DJ3EI

April 4,2015, Joe Taylor wrote:
> Hi Andreas,
>
> DJ3EI wrote:
>>> A detailed log of program changes since v1.3 r3673 is available here:
>>> http://physics.princeton.edu/pulsar/K1JT/wsjtx-1.4.0-rc5.log
>> Regarding this particular file, I have found a few nits to pick:
> The file in question, wsjtx-1.4.0-rc5.log, is *not* a troff file.  It's 
> a perfectly ordinary text file.  Any browser should be happy to download 
> the file. If the browser is not configured to display such a file 
> automatically, it will be happy to display it for you in NotePad, 
> WordPad, etc.  Or you can save yje file and open it in any text editor. 
>   Clicking on the filename in Windows Explorer will open it in NotePad.
>
> There's no need for and special UTF-8, etc., handling.  If you find a 
> few non-ascii characters in the file, you may safely ignore them.
>
> The purpose of this log file is to track changes in program code 
> whenever they have been committed to our repository.
>
>       -- 73, Joe, K1JT
>
>> The server tells my browser
>>
>>      Content-Type: application/x-troff-man
>>
>> (For people that have curl, this can be tested with
>>
>>      curl -I http://physics.princeton.edu/pulsar/K1JT/wsjtx-1.4.0-rc5.log
>>
>> with no need to download the whole file.)
>>
>> Why troff? This only causes brothers to refuse to display it.
>> I think a simple
>>
>>      Content-Type: text/plain; charset=utf-8
>>
>> would be better.
>>
>> We have two UTF-8 non-breaking spaces and one UTF-8 "ü" in the file.
>> So UTF-8 is called for, can't leave that out.
>>
>> But that does not fit entirely.  We have one instance of non-UTF-8 - coding, 
>> too:
>>
>>>           Version numbers are now stored in Versions.cmake and work in
>>>           concert with automatic svn revision lookup during build.  The
>>>           version string becomes 'rlocal'± if there are any uncommitted
>>>           changes in the build source tree.
>> There is this curious single byte, octal 261, behind the "'rlocal'".
>>
>> If iso-8859-1 coding were intended, this would produce the "±".  In
>> UTF-8, this byte makes no sense.   Personally, I'm not sure whether
>> that byte is signal (in which case it should be replaced by a UFT-8 ±)
>> or noise.
>>
>> Greetings,
>>
>> Andreas, DJ3EI
>>
>>
>>
>> Joe Tayloer wrote April 4, 2015:
>>
>>> The WSJT Development Group is pleased to announce Release Candidate 5
>>> for WSJT-X Version 1.4.0.  Installation packages for Windows, Linux, and
>>> OS X can be downloaded from the WSJT web site:
>>>
>>> http://physics.princeton.edu/pulsar/K1JT/wsjtx.html
>>>
>>> Release candidate 5 (wsjtx-1.4.0-rc5) is stable and reliable; there are
>>> just a few changes since -rc4.  All rig-control problems reported to us
>>> have been resolved.
>>>
>>> A detailed log of program changes since v1.3 r3673 is available here:
>>> http://physics.princeton.edu/pulsar/K1JT/wsjtx-1.4.0-rc5.log
>>>
>>> Upgrading from a previous release of v1.4 will be seamless; there is no
>>> need to uninstall a previous version or to move any files.
>>>
>>> If you are upgrading from WSJT-X v1.3 you must copy your log files into
>>> a new location and re-enter your setup information.  Full details and
>>> instructions are provided here:
>>> http://physics.princeton.edu/pulsar/K1JT/ReleaseNotice.txt
>>> You should also be sure to read the WSJT-X v1.4 User Guide.  (Note that
>>> some updates to the User Guide are still under way.)
>>>
>>> We expect that release candidate 5 will very soon become the "official"
>>> version 1.4.0 of WSJT-X.
>>>
>>> Most of you know that the next program version, WSJT-X v1.5, is also
>>> moving rapidly toward a first beta release.  More than 100 users have
>>> built this version themselves, from the open source code.  They have
>>> been exercising it thoroughly on the air, especially enjoying its
>>> improved decoding speed and other new features.  We plan to make
>>> installable packages for WSJT-X-1.5.0-rc1 available very soon.
>>>
>>> Version 1.6 is also progressing nicely, in a special development branch.
>>>    Again, many users are regularly building this version from source
>>> code.  It will be the first WSJT-X version to support
>>> VHF-UHF-Microwave-oriented modes from WSJT including JT4, JT65B, and JT65C.
>>>
>>>      -- 73 from Joe, K1JT, for the WSJT Development Group
>>>
>>> ------------------------------------------------------------------------------
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Dive into the World of Parallel Programming The Go Parallel Website, 
>> sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub for 
>> all
>> things parallel software development, from weekly thought leadership blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> _______________________________________________
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the 
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to