Re: [gopher] OverbiteFF 3.1 available
I second this request. Gophernicus has been able to do US-ASCII/Latin-1/UTF-8 for years (since day 1 basically) but it always defaulted to US-ASCII because no Gopher client could reliably parse anything else. Would be nice to have a default charset with more than 7 bits of data :D
- Kim
> On 09 Jan 2016, at 20:09, Mateusz Viste <mateusz@viste.fr> wrote:
>
> Just curious - do you plan some further maintenance on OverBite (some new versions popping out in the future?)
>
> If not that's fine of course, but if yes, then I'd like to suggest something that is bugging me since years: auto-selection of the charset, based on the CAPS "ServerDefaultEncoding" property :)
> If OverBite reads CAPS (and IIRC it does already, for some things), it might be easy perhaps to just emit a html "meta charset=" header when ServerDefaultEncoding contains a well-known value.
>
> Anyway, thank you again for this fresh version!
>
> cheers,
> Mateusz
>
>
> On 09/01/2016 18:24, Cameron Kaiser wrote:
>> This fixes multiple issues with Firefox 38+ and 44+, including disappearing
>> inline view support and double requesters. It is currently awaiting AMO
>> review and signing, but you can see it in the versions list.
>>
>> https://addons.mozilla.org/en-US/firefox/addon/overbiteff/versions/
>>
>> It is also compatible with TenFourFox and SeaMonkey.
>>
>
>
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
Reply to: