LP_XMLConverter Libpacks and password protected objects

[Piotr Dobrowolski]

Since some instructions on howto deal with translations in libpack is now published... I just wanted to try with existing library packed to lcf.

But I am hitting the wall hard way: LP_XMLConverter does not process libpack when the lcf that is part of the source folder contains password protected files...so the questions is: who the ... this functionality is for, maybe I do something wrong, but if the translation is only for open files then there is no point. I just wanted to experiment with the file system (files/folders) I have my own translation system inside the library.

[scottjm]

Which objects are giving password errors? I know in previous versions all objects are not password protected. 

If you have the object placed in Archicad and try to open it in the GDL editor does it prompt for a password?

from recollection during beta when I did some poking around with libpacks I did the following and could decompile everything:

-unpack the libpack

-unpack the lcf

- decompile all the gsms inside that to xml or hsf. 

[Piotr Dobrowolski]

Compiling libpack does not have -password option, and if incorporating in libpack a lcf with password protected gsm files, it fails.

[scottjm]

Hmmm odd. Does the libpak compile with the same lcf content that’s not password protected?

[Barry Kelly]

Does it work if you compile manually without the LP_XMLConverter?

Barry.

[Piotr Dobrowolski]

First I tried embedded command in AC, then LP_XMLConverter... the same error message. I will try creating the dummy library from scratch, and I will see what happens, (anyway such a demo should be there in the manual section: 1.libpack(ready), 2. source with gsms or so ...and and separate for each step to create a file&folder structure for translation and so on... so it can be treated as a sandbox. It is better than when I tried to decipher how it works from LP_XMLConverter embedded help, but still the manual is kind of 50:50.

I am about to implement libpack to VELUX library, it has to be password protected which is obvious... I have my own in-library translation system, so the only need is to implement the virtual file system, as for some markets it might be helpful.

[ZsuzsannaB]

Hi Piotr, 

Unfortunately, the .libpack format does not support password-protected GSM files, and as for now, there is no plan to do so.

I hope this answers your question.

Zsuzsi

[Piotr Dobrowolski]

I need to add alredy done lcf to the libpack - because I do not need to redo the process everytime the update goes, and I need to have te lcf to be compatible to ver 19 and upwards..

[Piotr Dobrowolski]

Bad decision IMHO, but it is working with libpacks loaded as folders...so it works, and *.libpack is a container file so it should work.

I hope You will change Your mind as the producers' bim libraries could need the translations.

I am developing VELUX library and I would make great use of changing the filesystem for different markets without recompiling the whole library.

[scottjm]

Ughhhh. 😣 Yet another frustration to deal with with lib packs.