Re: [hylafax]: the umlauts thing

Am 17.04.2018 um 16:31 schrieb Lee Howard:
> On 04/17/2018 06:51 AM, Carsten wrote:
>>
>>
>> Am 17.04.2018 um 12:15 schrieb Max Mothwurf:
>>> Hello Carsten
>>
>>> I think we need to clarify what hylafax version you are really=20
>>> using...I have
>>> to admit I did not check it when writing my answer
>>>
>>>> hylafax-server:
>>>> =A0=A0=A0 Installed: 3:6.0.6-6
>>>
>>> the 6.0.6 may point to the lastest release from hylafax.org, dated=20
>>> back to
>>> 2012. Quite surprised that this is still in use...but thats a=20
>>> different story.
>>> In this case - no. Hylafax uses a completely different localization t=
han
>>> hylafax+, where the patch refers to.
>>>
>>
>> Ah, ok, I never thought about the EOL and Version History in this.
>> So from what I understand right now, HylaFax is not updated since 2012=
=20
>> anymore?
>=20
> To be accurate...
>=20
> http://git.hylafax.org/
>=20
> ... the last commit was 2014-07-31.=A0 The commit previous to that was=20
> 2012-08-28.
>=20
>> And Hylafax+ ist somehow its own branch from the original Hylafax but=20
>> is updated further?
>=20
> The forking discussions are out there in the mailing list archives. In =
a=20
> nutshell, I was doing too much development for others to be comfortable=
,=20
> and so I felt like a fork would allow both sides to have what they=20
> wanted.=A0 I had hoped that the fork would be "collaborative"... and th=
at=20
> HylaFAX+ code development would make its way to the hylafax.org=20
> repository over time when those maintainers felt comfortable with it.
>=20
>> To which point in time? I see
>> "...
>> Feb 22 2017:=A0=A0=A0 Announcing HylaFAX+
>> ..."
>> on the web page at http://hylafax.sourceforge.net
>> Even so it is not that outdated as the "original" it still seems to=20
>> got stuck over a year ago. Am I right?
>=20
> To be accurate...
>=20
> https://sourceforge.net/p/hylafax/HylaFAX+/HEAD/tree/
>=20
> ... the last commit was 2018-02-22.=A0 The commit previous to that was =
the=20
> day previous.=A0 But, hopefully you can see that the development is act=
ive.
>=20
> There hasn't been a release for a year because the released code is=20
> quite stable.=A0 I don't want to disrupt stable releases without reason=
=20
> benefiting the general base of users.
>=20
>>
>> Is there some living branch of it?
>=20
> What do you mean by living?
>=20
>> Is it reliable at all to count on Hylafax(+) if it goes to future=20
>> developement?
>=20
> Open source software is yours to do with whatever you choose.=A0 If you=
=20
> rely on others' decisions then you should get informed so that you know=
=20
> what you can rely on and what you can't.
>=20
> Thanks,
>=20
> Lee.

Thanks for the quick reply. That's what I call "living" ;-) --> "it's=20
alive, muhahaaaa" <---

I scratched the debate about the two branches but I pulled back before=20
dropping into the rabbits hole. So I leave the decissions about that to=20
those who do the coding.

I posted a request to the lemakers forum, if there is anybody that can=20
feed the repositories with a version of HylaFax+. I'll see, if anybody=20
feels comfortable to do so.

For the moment this does not solve my issue with the "Umlauts" but I got=20
it boxed for now, so at least I know, which way to dig.

br
Carsten


>=20
>=20
>=20
> ____________________ HylaFAX(tm) Users Mailing List ___________________=
____
>  =A0To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/ls=
g2.cgi
> On UNIX: mail -s unsubscribe [email protected] < /dev/n=
ull
>  =A0*To learn about commercial HylaFAX(tm) support, mail [email protected]=
.*
>=20


____________________ HylaFAX(tm) Users Mailing List _____________________=
__
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.c=
gi
 On UNIX: mail -s unsubscribe [email protected] < /dev/nu=
ll
  *To learn about commercial HylaFAX(tm) support, mail [email protected].*