Hi,
> On Mar 21, 2022, at 7:21 PM, Jim Hall wrote:
>
> On Mon, Mar 21, 2022 at 5:41 PM Mark Olesen wrote:
>>
>> Is it not possible to create maco wrappers around the new api to
>> retain compatibility with the old? Sorry for my ignorance, I never
>> used FD-NLS libraries. I would think it
On Mon, Mar 21, 2022 at 5:41 PM Mark Olesen wrote:
>
> Is it not possible to create maco wrappers around the new api to
> retain compatibility with the old? Sorry for my ignorance, I never
> used FD-NLS libraries. I would think it should be seamless and
> transparent. For me, the biggest change
Is it not possible to create maco wrappers around the new api to
retain compatibility with the old? Sorry for my ignorance, I never
used FD-NLS libraries. I would think it should be seamless and
transparent. For me, the biggest change would be migrating data files.
On Mon, Mar 21, 2022 at 11:11
Hi Mark,
> On Mar 21, 2022, at 1:27 PM, Mark Olesen wrote:
>
> https://www.gnu.org/software/gettext/
>
> Port then migrate your current translations to PO format
That’s not going to happen. We can’t even find enough people to fix some minor
years-old bugs. Expecting someone to rewrite all of
https://www.gnu.org/software/gettext/
Port then migrate your current translations to PO format
On Mon, Mar 21, 2022 at 4:56 AM Jerome Shidel wrote:
>
> Hi all,
>
> As many of you are probably already aware, a while back I started
> coordinating language translations for FreeDOS and related
Hi all,
As many of you are probably already aware, a while back I started coordinating
language translations for FreeDOS and related projects over on GitHub in the
FD-NLS project[1]. The translators that have been contributing do a great job.
But with all the various formats and methods used
