Language files oddities

[Kulle]

Language files oddities

When I use in Porteus 5.0 the old version evince-3.20.2-x86_64-1_sonly
the menu is in German.
When I use in Porteus 5.0 the new version evince-3.36.5
the menu is in English.
Why?

[Blaze]

Kulle, seems need to build evince via this Slackbuild https://slackbuilds.org/repository/15.0/office/evince/ and you will get German localization

[ncmprhnsbl]

there's also prebuilt packages: https://slakfinder.org/index.php?act=se ... e=#results
requires (at the least) libhandy :https://slakfinder.org/index.php?act=se ... e=#results

[Kulle]

Thanks ncmprhnsbl and Blaze

[Rava]

I looked for pre-made Slackware packages via https://slakfinder.org and a search for it only on x86-64 Slack15.0 only gave two evince versions: both V41.3
Searching for all via https://slakfinder.org/index.php?act=se ... e=#results gives me also versions like
3.28.5
3.12.2
etcetera.

Why the huge difference in version numbering?
41.2 sounds like ages ahead compared to 3.28.5

I choose two versions to compare and their .txt files looked identical, but I decided to make a diff.

I downloaded both .txt files:

Code: Select all

guest@porteus:/tmp$ wget https://slakfinder.org/sbomt64-15.0/office/evince/evince-41.3-x86_64-1smt.txt
[…]
Length: 438 [text/plain]
[…]
2022-10-02 06:39:26 (72.1 MB/s) - ‘evince-41.3-x86_64-1smt.txt’ saved [438/438]

guest@porteus:/tmp$ wget https://packages.slackonly.com/pub/packages/14.2-x86_64/office/evince/evince-3.28.5-x86_64-1_slonly.txt
[…]
Length: 438 [text/plain]
[…]
2022-10-02 06:39:43 (69.5 MB/s) - ‘evince-3.28.5-x86_64-1_slonly.txt’ saved [438/438]

and compared them

Code: Select all

guest@porteus:/tmp$ ls -o evince-*
-rw-r--r-- 1 guest 438 2020-01-14 14:11 evince-3.28.5-x86_64-1_slonly.txt
-rw-r--r-- 1 guest 438 2022-05-30 08:39 evince-41.3-x86_64-1smt.txt
guest@porteus:/tmp$ diff evince-*
guest@porteus:/tmp$ 

As I presumed, they are identical.
So why the huge version difference, in my compared cases between 3.28.5 and 41.3 ?

[Rava]

I created a new thread for my issues with evince and XFCE:
evince-41.3-x86_64-1 for Port 5.0 XFCE in xzm module requests

[Ed_P]

Maybe some of the problems you are encountering are due to you not running Porteus 5.0 XFCE. You are using an older version of XFCE which has different driver files and maybe other differences also.

What I did with my 5.0rc3 wifi problems is compare (diff) a nucleus that Blaze created with iwlwifi support to the one in the 5.0rc3 ISO then created a module (dir2xzm) of the /lib/firmware/iwlwifi-* files. Can't you do that with for your video problems in the XFCE DEs?

[Rava]

Maybe some of the problems you are encountering are due to you not running Porteus 5.0 XFCE. You are using an older version of XFCE which has different driver files and maybe other differences also.

My XFCE is compiled by Fulalas specifically for Porteus 5.0.
Look at the date it was created, or look into the thread where he published the link.

[Ed_P]

My XFCE is compiled by Fulalas specifically for Porteus 5.0.

Yes Xfce 4.12 for Porteus 5 final release but it is still not the same as the 2022-05-05 XFCE in the 5.0 XFCE ISO so problems you experience with it may be unique to you. Does the XFCE module in the ISO support your hardware? Did you rebuild the ISO with the older XFCE module or are you adding it via /modules and a cheatcode?

[Rava]

Yes Xfce 4.12 for Porteus 5 final release

Exactly.

but it is still not the same as the 2022-05-05 XFCE in the 5.0 XFCE ISO

Of course it's not, since that one is XFCE 4.16 while my version is, as you quoted, "Xfce 4.12 for Porteus 5 final release"

problems you experience with it may be unique to you.

There are others who use XFCE 4.12 on Porteus, not just me, so no, the problems I experience with it cannot be unique to me.

Does the XFCE module in the ISO support your hardware?

I suppose it does.

Did you rebuild the ISO with the older XFCE module or are you adding it via /modules and a cheatcode?

Neither.


I use several Porteus_5.0whatever/porteus/base folders as my setup. Almost all are addressed via UUID and their folder name and the porteus-v5.0-x86_64.cfg inside of these, e.g. currently that translates into this:

Code: Select all

guest@porteus:~$ echo $PORTDIR/porteus-v5.0-x86_64.cfg 
/mnt/sda1/Porteus_5.0/porteus/porteus-v5.0-x86_64.cfg

Since XFCE is my main DE and XFCE 4.12 is my XFCE for years now, I do not specify anything in the folder name.

I reserve the first few characters [a-f] … for testing purposes. (Currently using a b d e f and x); The rest are the first characters of the DE it incorporates with one difference in how I address Cinnamon.
A setup for Cinnamon does have the addition of "z" since Cinnamon = Zimt in German, and
A setup for KDE5 does have the addition of "k" and so on.

Look for yourself:
The folders:

Code: Select all

guest@porteus:/mnt/sda1$ ls -1d Porteus_5.0*[abdefgkmoxz]/ Porteus_5.0/
Porteus_5.0/
Porteus_5.0a/
Porteus_5.0b/
Porteus_5.0d/
Porteus_5.0e/
Porteus_5.0f/
Porteus_5.0g/
Porteus_5.0k/
Porteus_5.0m/
Porteus_5.0o/
Porteus_5.0x/
Porteus_5.0z/
Porteus_5.0wrea/

and the 003* modules in base/ of the Porteus_5.0*[abdefgkmoxz] folders

Code: Select all

guest@porteus:/mnt/sda1$ ls -1d Porteus_5.0*[abdefgkmoxz]/porteus/base/003*
Porteus_5.0a/porteus/base/003-xfce-4.12-20220218.xzm
Porteus_5.0b/porteus/base/003-xfce-4.12-20220725.xzm
Porteus_5.0d/porteus/base/003-xfce-4.12-20211224.xzm
Porteus_5.0e/porteus/base/003-xfce-4.12-20220114.xzm
Porteus_5.0f/porteus/base/003-xfce-4.12-20220114.xzm
Porteus_5.0g/porteus/base/003-gnome.xzm
Porteus_5.0k/porteus/base/003-kde5.xzm
Porteus_5.0m/porteus/base/003-mate.xzm
Porteus_5.0o/porteus/base/003-openbox-x86_64-20210110.xzm
Porteus_5.0x/porteus/base/003-xfce-4.16-20210127_rava-fix.xzm
Porteus_5.0z/porteus/base/003-cinnamon.xzm
Porteus_5.0wrea/porteus/base/003-xfce-4.12-20211115.xzm

[Ed_P]

I use several Porteus_5.0whatever/porteus/base folders as my setup. Almost all are addressed via UUID and their folder name

And that's wonderful and what makes you such a good tech. But new users are going to relate your XFCE postings as being the 5.0 released ISO version and be confused trying to find solutions to their XFCE ISO system problems.

My main concern is new users, especially if they are new Linux users and even more especially if they are new Windows users to Linux.

Added in 5 minutes 57 seconds:
An example is your "evince-41.3-x86_64-1 for Port 5.0 XFCE" thread. Is that about the official Porteus 5.0 XFCE ISO that someone has spent time downloading or your XFCE 4.12 system.

Maybe adding 4.12 to all your XFCE postings would help.

[Rava]

An example is your "evince-41.3-x86_64-1 for Port 5.0 XFCE" thread. Is that about the official Porteus 5.0 XFCE ISO that someone has spent time downloading or your XFCE 4.12 system.

Maybe adding 4.12 to all your XFCE postings would help.

Then look at the very first paragraph of that posting of yours truly.
There it reads this:

Tried getting evince ( as I stumbled upon it here: Language files oddities ) to run under Port 5.0 XFCE 4.12:

(highlighting by me)

[Ed_P]

look at the very first paragraph of that posting of yours truly

Yes, that's true and nice but it requires one read the postings rather than just scan the titles.

[Rava]

it requires one read the postings

That should be a given.

[Ed_P]

Most of us don't have time to read every single posting.