Re: Mark utf8x as "deprecated" ?
On Wed, Feb 28, 2024 at 05:40:39PM +0100, Jean-Marc Lasgouttes wrote: > Le 28/02/2024 à 02:11, Scott Kostyshak a écrit : > > That is indeed good to know. I don't think we should remove the support, > > just signal to the user that it's not recommended anymore. > > Then "obsolete" might be a better wording (deprecated means to me that we > plan to ditch it). Ah yes that is a very good point. Also "deprecated" doesn't signal whether LyX is planning to deprecate support (not the case) or whether it is just referring to the state of upstream TeX. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Mark utf8x as "deprecated" ?
Le 28/02/2024 à 02:11, Scott Kostyshak a écrit : That is indeed good to know. I don't think we should remove the support, just signal to the user that it's not recommended anymore. Then "obsolete" might be a better wording (deprecated means to me that we plan to ditch it). JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Mark utf8x as "deprecated" ?
On Wed, Feb 28, 2024 at 10:06:24AM +, José Matos wrote: > On Tue, 2024-02-27 at 20:11 -0500, Scott Kostyshak wrote: > > That is indeed good to know. I don't think we should remove the > > support, > > just signal to the user that it's not recommended anymore. > > > > Scott > > Honestly, I suspect, it probably means that since it works the authors > do not care. :-) I think you're right, although I wonder if it will continue to work. > So probably the first step is to signal that to developers/writers and > to see if that it is still needed or a remnant from the past... > > I am becoming nostalgic with time. :-D Fair enough ;). Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Mark utf8x as "deprecated" ?
On Tue, 2024-02-27 at 20:11 -0500, Scott Kostyshak wrote: > That is indeed good to know. I don't think we should remove the > support, > just signal to the user that it's not recommended anymore. > > Scott Honestly, I suspect, it probably means that since it works the authors do not care. :-) So probably the first step is to signal that to developers/writers and to see if that it is still needed or a remnant from the past... I am becoming nostalgic with time. :-D Best regards, -- José Abílio -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Mark utf8x as "deprecated" ?
On Tue, Feb 27, 2024 at 11:39:22PM -0500, Richard Kimberly Heck wrote: > On 2/27/24 20:12, Scott Kostyshak wrote: > > On Mon, Feb 26, 2024 at 08:40:03PM -0500, Richard Kimberly Heck wrote: > > > On 2/26/24 11:20, Scott Kostyshak wrote: > > > > I do not propose this for now since it is a string change, but should we > > > > mark utf8x support as deprecated in the dropdown box? Just to give a > > > > hint that it is probably not what users want? If so, should I do this on > > > > the master branch after 2.4.0 is out so that it will go into effect for > > > > 2.5.0? Note that I am just suggesting to add the string "(deprecated)", > > > > and not to remove the support. > > > > > > > > I don't know anything about the technical details, but a utf8x test > > > > started failing after a TL update, and I do not think it is expected for > > > > it to be fixed. See here: > > > > > > > > > > > > https://github.com/latex3/hyperref/issues/248#issuecomment-1961868947 > > > I don't know anything at all, really, about language support and > > > encodings, > > > but it's fine of course to add new strings for 2.4.1 (if it is not an > > > emergency release). > > That is good to know. It feels a bit weird to deprecate something during > > a minor release. I don't have a strong preference though. > > If we were deprecating it in the sense of "We might no longer support this", > that would be one thing. But it's more in the sense of "You might want to > know that this may not be supported in LaTeX itself for very much longer". True, that's an important distinction. In that case I'm in favor of doing it for 2.4.1. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Mark utf8x as "deprecated" ?
On 2/27/24 20:12, Scott Kostyshak wrote: On Mon, Feb 26, 2024 at 08:40:03PM -0500, Richard Kimberly Heck wrote: On 2/26/24 11:20, Scott Kostyshak wrote: I do not propose this for now since it is a string change, but should we mark utf8x support as deprecated in the dropdown box? Just to give a hint that it is probably not what users want? If so, should I do this on the master branch after 2.4.0 is out so that it will go into effect for 2.5.0? Note that I am just suggesting to add the string "(deprecated)", and not to remove the support. I don't know anything about the technical details, but a utf8x test started failing after a TL update, and I do not think it is expected for it to be fixed. See here: https://github.com/latex3/hyperref/issues/248#issuecomment-1961868947 I don't know anything at all, really, about language support and encodings, but it's fine of course to add new strings for 2.4.1 (if it is not an emergency release). That is good to know. It feels a bit weird to deprecate something during a minor release. I don't have a strong preference though. If we were deprecating it in the sense of "We might no longer support this", that would be one thing. But it's more in the sense of "You might want to know that this may not be supported in LaTeX itself for very much longer". Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Mark utf8x as "deprecated" ?
On Mon, Feb 26, 2024 at 08:40:03PM -0500, Richard Kimberly Heck wrote: > On 2/26/24 11:20, Scott Kostyshak wrote: > > I do not propose this for now since it is a string change, but should we > > mark utf8x support as deprecated in the dropdown box? Just to give a > > hint that it is probably not what users want? If so, should I do this on > > the master branch after 2.4.0 is out so that it will go into effect for > > 2.5.0? Note that I am just suggesting to add the string "(deprecated)", > > and not to remove the support. > > > > I don't know anything about the technical details, but a utf8x test > > started failing after a TL update, and I do not think it is expected for > > it to be fixed. See here: > > > >https://github.com/latex3/hyperref/issues/248#issuecomment-1961868947 > > I don't know anything at all, really, about language support and encodings, > but it's fine of course to add new strings for 2.4.1 (if it is not an > emergency release). That is good to know. It feels a bit weird to deprecate something during a minor release. I don't have a strong preference though. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Mark utf8x as "deprecated" ?
On Mon, Feb 26, 2024 at 05:46:15PM +, José Matos wrote: > On Mon, 2024-02-26 at 11:20 -0500, Scott Kostyshak wrote: > > I do not propose this for now since it is a string change, but should > > we > > mark utf8x support as deprecated in the dropdown box? Just to give a > > hint that it is probably not what users want? If so, should I do this > > on > > the master branch after 2.4.0 is out so that it will go into effect > > for > > 2.5.0? Note that I am just suggesting to add the string > > "(deprecated)", > > and not to remove the support. > > > > I don't know anything about the technical details, but a utf8x test > > started failing after a TL update, and I do not think it is expected > > for > > it to be fixed. See here: > > > > > > https://github.com/latex3/hyperref/issues/248#issuecomment-1961868947 > > > > Scott > > The following Hebrew documents still use it in 2.4: > > lib/doc/he/Intro.lyx > lib/doc/he/Tutorial.lyx > lib/examples/he/Example_%28LyXified%29.lyx > lib/examples/he/Example_%28raw%29.lyx > lib/examples/he/Welcome.lyx That is indeed good to know. I don't think we should remove the support, just signal to the user that it's not recommended anymore. Scott > > FWIW this has not changed since 2.1. > -- > José Abílio > -- > lyx-devel mailing list > lyx-devel@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-devel signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Mark utf8x as "deprecated" ?
On 2/26/24 11:20, Scott Kostyshak wrote: I do not propose this for now since it is a string change, but should we mark utf8x support as deprecated in the dropdown box? Just to give a hint that it is probably not what users want? If so, should I do this on the master branch after 2.4.0 is out so that it will go into effect for 2.5.0? Note that I am just suggesting to add the string "(deprecated)", and not to remove the support. I don't know anything about the technical details, but a utf8x test started failing after a TL update, and I do not think it is expected for it to be fixed. See here: https://github.com/latex3/hyperref/issues/248#issuecomment-1961868947 I don't know anything at all, really, about language support and encodings, but it's fine of course to add new strings for 2.4.1 (if it is not an emergency release). Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Mark utf8x as "deprecated" ?
On Mon, 2024-02-26 at 11:20 -0500, Scott Kostyshak wrote: > I do not propose this for now since it is a string change, but should > we > mark utf8x support as deprecated in the dropdown box? Just to give a > hint that it is probably not what users want? If so, should I do this > on > the master branch after 2.4.0 is out so that it will go into effect > for > 2.5.0? Note that I am just suggesting to add the string > "(deprecated)", > and not to remove the support. > > I don't know anything about the technical details, but a utf8x test > started failing after a TL update, and I do not think it is expected > for > it to be fixed. See here: > > > https://github.com/latex3/hyperref/issues/248#issuecomment-1961868947 > > Scott The following Hebrew documents still use it in 2.4: lib/doc/he/Intro.lyx lib/doc/he/Tutorial.lyx lib/examples/he/Example_%28LyXified%29.lyx lib/examples/he/Example_%28raw%29.lyx lib/examples/he/Welcome.lyx FWIW this has not changed since 2.1. -- José Abílio -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
