Domino on Linux/Unix, Troubleshooting, Best Practices, Tips and more ...

Notes Client all languages in one package

Daniel Nashed  12 June 2020 14:22:51
To include  dictionaries was very high on my personal priority list for a while.
I don't want to install a German client just to have German spell-checking.

And this is true for may customer environments who need multiple languages.


And I customer asked me about multi language kits today.

We have many different kits today per languages + MUI packs.


What we have today is complicated and confusing.


I found an AHA idea asking for packs that include all languages.

And I really like the idea to have one English version with all dictionaries and one kit that contains all languages!


The idea has 7 votes today ->
https://domino-ideas.hcltechsw.com/ideas/NTS-I-1220

If you think this would simplify deployments and just adds a bit more of space, add yourself to the wish-list item ;-)


And I would be very interested to hear your feedback.
I am not really a client guy. But I run into those kind of things quite often in customer deployments.


-- Daniel

Comments

1Christian Henseler  12.06.2020 15:22:53  Notes Client all languages in one package

Although it is already possible today to combine all kinds of languages with the existing separate MUI installers into one single installation package, I support the idea.

My experience with various customers is that there is the need for an easy/easier to deploy/install package.

Including all languages in one single installation package will help most customers to achieve this.

A > 1 GB size installation package is not uncommon nowadays, and with contemporary techniques like pre install caching and peer to peer deployment, the size of an installation packages is only a problem in very distinct use cases.

Those guys (me!?) who prefer a specially tailored install package will still be able to build such, but 99 % of customers will/would prefer a one fits all install packages, I assume

2Sebastian Spudik  12.06.2020 19:12:49  Notes Client all languages in one package

I like that idea, too and voted for it.

I think, nowadays it is essential to have one installation with different languages or to have the abillity to switch between languages.

3Florian Vogler  12.06.2020 21:16:34  Notes Client all languages in one package

Personally I’d be in favor of separating languages from installer.

So that one can drop 0-n additional languages into same directory of installer and it just adds them.

That would come with the benefit of not deploying 1 gb to then only install one additional language.

I’d even promote going a step further and separating dictionaries from ui languages / templates.

It’d be awesome to add 0-n zu languages (binaries and templates) and 0-n dictionaries, both independently.

It would also greatly simplify the „baking all the installers“ effort imo.

4Ben Langhinrichs  12.06.2020 22:00:31  Notes Client all languages in one package

Wait, there are languages other than English? (Sorry, I'm American.)

5Christian Henseler  13.06.2020 21:00:45  Notes Client all languages in one package

@Florian:

The situation you describe does already exist today.

With MUI Packs and XTAF Dictionaries, you can add any language to a given installation independently.

But most of the Software deployment guys I talk at customers with, don't like it.

Furthermore, most of the Software deployment guys don't know anything beside MSI, so the knowhow to combine Eclipse installer parts from various MUI Packs into one installer is not widely spread.

You need to know how the Notes Installer and MUI Packs are built and this knowledge is not very common.

With SCCM on Windows 10 you loose control when a specific installation package gets installed and if you want to manage that, it gets complicated.

As a result, I think a big "one fits all" install package is more suited for most customers than combining many small installation packages to get what you want.

6Daniel Nashed  14.06.2020 8:20:21  Notes Client all languages in one package

IMHO it is all about making it simple.

Imagine the reduction of packages to look for, to manage at HCL side..

And on the customer side this would simplify the deployment dramatically!

Today to get a directionary deloyed to you have to integrate it into your installer (complicated). Or to install the whole langauge.

You can also create your own installer -- also complicated.

For multiple languages it looks different. You have full client versions and MUI packs.

Look into how many different options we have today.

I don't think the size makes a huge difference!

And I think having a.) English with all dictionaries for Ben ;-) and b.) One with all languages makes a lot of sense!

Other software provides you an network based installer, which downloads just what is requested.

But that would be too much work to implement.

Modern software deployment infrastructure should not have an issue deploying a 1 GB install image.

-- Daniel

Archives


  • [IBM Lotus Domino]
  • [Domino on Linux]
  • [Nash!Com]
  • [Daniel Nashed]