topic Re: Libpack and folder/file structure (not reading the translation) in GDL

Libpack and folder/file structure (not reading the translation)

Piotr Dobrowolski — Mon, 25 Nov 2024 11:51:45 GMT

I am trying to uderstand how the folder structure translation works. I have created a dummy library with 3 files. All what I need is the folder/file structure change, so I do not need now *.po files, just pathNameTable*.json. I did only INT for the sandboxing.

I cannot get it to work, probably some silly mistake.

Loading this folder as a libpack does load it straight without translating the path.

Can anyone help with it? Please

Re: Libpack and folder/file structure (not reading the translation)

ZsuzsannaB — Mon, 25 Nov 2024 14:13:35 GMT

Hi Piotr!

I'm not sure I understand your exact issue; please help me clarify a few things first so that I can help.

Do you mean by "loading this folder as a libpack" that you have compiled it with the LP_XMLConverter into .libpack format?

By "without translating the path", do you mean it doesn't change to the virtual paths defined in the pathnametable file?

Re: Libpack and folder/file structure (not reading the translation)

Piotr Dobrowolski — Mon, 25 Nov 2024 17:27:23 GMT

Hi,

I need only to apply the directory/filenames changes while translation is done, so I assume I have to include only pathNameTable*.json. I did myself a sandbox library with 3 objects in 3 libraries. In the sandbox I included only INT translation.

For testing purposes I initiated the option in GDL editing toolbar so AC 28 interprets the folder content as a libpack.

Anyway it does not work with the changes in pathNameTable*.json, I probably did a silly mistake...because I checked in some of the GLOBAL Lib libpacks and it should work.

So I need to know what I did wrong 😛

Re: Libpack and folder/file structure (not reading the translation)

Barry Kelly — Tue, 26 Nov 2024 01:16:51 GMT

We really do need some documentation about these library packs, what are the individual files within them for, how are they edited, what references what, how are they packaged together.

If this documentation is available, please share where it is, as it is not obvious to me.

I assume there will be many 3rd party library makers wanting to create library packages.

Also how to convert a library mapping table JSON file into a CSV file.

In the video (at 2.00) it shows the conversion, but it is not clear (to me at least) what file is run to make that conversion.

Barry.

Re: Libpack and folder/file structure (not reading the translation)

ZsuzsannaB — Tue, 26 Nov 2024 07:45:43 GMT

Dear Barry,

The documentation is available on the GDL center for 3rd party developers! You can find it here.

You can also find a less technical overview of library packages here under Library Documentation.

Let me know if you still have questions after reading them!

Best regards,

Zsuzsi

Re: Libpack and folder/file structure (not reading the translation)

ZsuzsannaB — Tue, 26 Nov 2024 07:58:58 GMT

Hello,

Thank you for the clarification; I just wanted to be on the same page about your workflow to replicate it and see what might be missing. 🙂

I'm still searching for the solution.

Regards,

Zsuzsi

Re: Libpack and folder/file structure (not reading the translation)

Barry Kelly — Tue, 26 Nov 2024 08:11:03 GMT

Thanks @ZsuzsannaB

There is a bit to read there but it looks like it covers what is what.

While I have you though, in the movie about modifying the mapping table that can be extracted from a template, at about the 2.00 minute mark, it shows converting the mapping value JSON file to a CSV file so it can be edited in Excel.

This is the movie link ...

https://graphisoft.sharefile.com/share/view/s852df7d2f10f47708082f329e3cc32d8

Is that also done with the LP_XMLConverter ?

Or is there some other magic involved.

I can't figure out what needs to be run or typed to do the conversion.

I have manually edited the JSON file in a text editor, but I would really like to know how to convert it to CSV so I can easily edit just the parts I want.

Thanks,

Barry.

Re: Libpack and folder/file structure (not reading the translation)

ZsuzsannaB — Tue, 26 Nov 2024 08:13:23 GMT

Your issue is in the package.info file. Try adding the empty <Dependencies></Dependencies> tag, so that the info file is valid. 🙂

Re: Libpack and folder/file structure (not reading the translation)

Piotr Dobrowolski — Tue, 26 Nov 2024 09:01:20 GMT

Unfortunately it is not the case 😞 I tested it also with this tag, without it, and fully copied tag from the libpack I have extracted from global library.

when loading the whole thing it always show as the native path in lcf.

json file looks like this:

and in AC:

So I am missing something that triggers the translation some way 😞

Re: Libpack and folder/file structure (not reading the translation)

ZsuzsannaB — Tue, 26 Nov 2024 09:08:18 GMT

I have tested your folder, that's why I suggested this, because without this tag, it didn't work for me either. The same applies to the localizationData.info file. Even if you don't have dictionaries, you need the empty tag in the file and so on. I've attached a version that works for me.

My last resort is, maybe try checking if your Localization Preferences are set to "INT".

Re: Libpack and folder/file structure (not reading the translation)

Piotr Dobrowolski — Tue, 26 Nov 2024 09:11:08 GMT

There is instruction, what i miss here - is something I am trying to do myself: a sandbox library that works, and can be edited just to see how the changes apply.

Create a New .libpack from Scratch/Upgrade .lcf to .libpack | GRAPHISOFT GDL Center

In the end of the day we both probably need to update the already done libraries to libpack mode (for 28+ versions) and keep the sole lcf for the lower versions, with as small changes as possible to reduce housekeeping.

Re: Libpack and folder/file structure (not reading the translation)

ZsuzsannaB — Tue, 26 Nov 2024 09:36:34 GMT

I have uploaded the working version of your sandbox in my previous reply.

If you have any exact questions or need clarification regarding the process explained in the documentation, I am happy to help.

Wishing you good luck,

Zsuzsi

Re: Libpack and folder/file structure (not reading the translation)

Piotr Dobrowolski — Tue, 26 Nov 2024 10:25:52 GMT

Thanks a lot,

I missed that in the first read 😞

Funny when I added that mysefl it did not work

~~And as I see the whole guid part is not actually needed, that's easier~~ 🙂 wrong assumption

I got it working with VELUX library as a folder, but still cannot do .libpack since objects are password protected in lcf

(https://community.graphisoft.com/t5/GDL/LP-XMLConverter-Libpacks-and-password-protected-objects/m-p/640961#M7165)