How to Install and Uninstall ruby3.0-rubygem-gettext_i18n_rails_js Package on openSuSE Tumbleweed
Last updated: December 22,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "ruby3.0-rubygem-gettext_i18n_rails_js" package
Learn how to install ruby3.0-rubygem-gettext_i18n_rails_js on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
ruby3.0-rubygem-gettext_i18n_rails_js
Copied
2. Uninstall "ruby3.0-rubygem-gettext_i18n_rails_js" package
In this section, we are going to explain the necessary steps to uninstall ruby3.0-rubygem-gettext_i18n_rails_js on openSuSE Tumbleweed:
$
sudo zypper remove
ruby3.0-rubygem-gettext_i18n_rails_js
Copied
3. Information about the ruby3.0-rubygem-gettext_i18n_rails_js package on openSuSE Tumbleweed
Information for package ruby3.0-rubygem-gettext_i18n_rails_js:
--------------------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : ruby3.0-rubygem-gettext_i18n_rails_js
Version : 1.3.0-1.20
Arch : x86_64
Vendor : openSUSE
Installed Size : 93,9 KiB
Installed : No
Status : not installed
Source package : rubygem-gettext_i18n_rails_js-1.3.0-1.20.src
Summary : Extends gettext_i18n_rails making your .po files available to client
Description :
It will find translations inside your .js and .coffee files, then it will
create JSON versions of your .PO files and will let you serve them with the
rest of your assets, thus letting you access all your translations offline
from client side javascript.
--------------------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : ruby3.0-rubygem-gettext_i18n_rails_js
Version : 1.3.0-1.20
Arch : x86_64
Vendor : openSUSE
Installed Size : 93,9 KiB
Installed : No
Status : not installed
Source package : rubygem-gettext_i18n_rails_js-1.3.0-1.20.src
Summary : Extends gettext_i18n_rails making your .po files available to client
Description :
It will find translations inside your .js and .coffee files, then it will
create JSON versions of your .PO files and will let you serve them with the
rest of your assets, thus letting you access all your translations offline
from client side javascript.