Hi,
> On Aug 31, 2022, at 2:36 PM, Paul Dufresne via Freedos-devel
> wrote:
>
>
> I am trying to do a 12.2.0 packagte for GCC.
> I am editing LSM files on Linux... and beginning to ask myself how much bad
> it is.
> I means... I am probably transforming them to UTF-8 unicode... so the
> codepage indicated in the file would be wrong now.
> And if I would edit them in DOS... I would have to change code page before
> editing any of them... I would guess.
> So... can I edit them in UTF-8 unicode... is there a tool that check that and
> add the modified-date?
>
First, you don’t need to worry about the modified-date field. If the field is
not present, the repository management utilities will add it automatically when
the package is added to a repository.
As for the basic LSM meta-data file, that needs to be in DOS codepage 437.
The language specific files in that directory must be in the appropriate DOS
codepage for that language. The fields in those language specific files work
like overrides to the standard English version (LSM).
For example, the English contains a version field. But, that field is excluded
from the language specific version. So, when the version is updated, all
languages show the new version. However, each language has its own description
and summary field. So, those are shown for that language instead of the default
English when using programs like FDIMPLES.
For packages that are kept on the official repository and/or provided on the
various release media, there is some additional things to be consider.
The master English meta-data always lives in the packages. However, the
translations for the package metadata lives over at the FD-NLS project[1] in a
couple big language specific CSV files.
That data gets staged in the GitLab FreeDOS Archive[2]. Which is used to
assemble packages for the releases and for the update repository on ibiblio[3].
The easiest way to edit those massive CSV files for the language specific
metadata is through the FD-NLS Desktop App[4] that I created. There are
Windows, Linux and macOS versions.
The app is pretty code at editing those and does all the UTF/Codepage
conversion stuff automatically. It has a live simulation/preview of what the
metadata will look like in DOS using FDIMPLES and some other features.
Eventually, it will support working on actual translations for the individual
programs as well as their metadata. But unfortunately, I just don’t have the
time to work on it at present.
:)
Jerome
[1] https://github.com/shidel/fd-nls
[2] https://gitlab.com/FreeDOS
[3]
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/indexes.html
[4] https://up.lod.bz/FDNLS_LNX
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
