Question about instructions for installing additional languages

[wfarrell]

I see in the documentation about installing additional languages the following statement:

NB: If you are using a style other than prosilver or subsilver2 you will need to copy the /styles/prosilver/theme/XX folder in to into the theme folder of your custom style.

I think that reference to "other than prosilver or subsilver2" may be incorrect. Should that really say "If you are using a style that is not based on prosilver you will need to copy...." instead?

Also, those instructions don't say anything about the language packs containing a folder named /ext, and also needing to upload that to the board. That part of the instructions should probably be updated.

[ssl]

To put it simply, you download the zip file of the language to add to your board, once the file has been decompressed, you send these 3 files to your server:

• /ext
• /styles
• /language

Obviously the /styles folder only concerns the prosilver style, it is the basic style of phpBB. For any other style installed on your board, it's up to you to adapt.

[wfarrell]

Obviously the /styles folder only concerns the prosilver style, it is the basic style of phpBB. For any other style installed on your board, it's up to you to adapt.

Thanks. Yes, that's clear.

However, my question is whether it is truly necessary to copy the /styles info into other styles that are based on prosilver. In that case, I would expect them to inherit from prosilver, which will already contain the info after it was uploaded the first time.

I would expect that the statement about copying "/styles/prosilver/theme/XX folder in to into the theme folder of your custom style" would only be needed for styles that don't inherit from prosilver.

Edit: Plus, of course, it would be nice for the official instructions to be complete, and mentiion /ext

[ssl]

It is obvious that a child style of prosilver will inherit the parameters of prosilver, so it is not useful to copy a folder into the child style.

[warmweer]

Edit: Plus, of course, it would be nice for the official instructions to be complete, and mentiion /ext

If extensions have language files: they are already packed within the extension

e.g. Usermap >>>/mot/usermap also contains /language which (if the extension install instructions are followed), will automatically be extracted).

So the phpBB instructions do not need mentioning of extension language files (when an extension is disabled/data deleted and then extension directory deleted, the extension language files are automatically deleted as these are/were part of the extension.

[ssl]

Edit: Plus, of course, it would be nice for the official instructions to be complete, and mentiion /ext

Why that ?
phpBB is software provided without an extension, except of course Vigilink because it is the only extension provided with phpBB, so adding a language file to phpBB does not concern any other extension than the one embedded with the software

[danieltj]

Edit: Plus, of course, it would be nice for the official instructions to be complete, and mentiion /ext

Why that ?
phpBB is software provided without an extension, except of course Vigilink because it is the only extension provided with phpBB, so adding a language file to phpBB does not concern any other extension than the one embedded with the software

Because it's better to be verbose than to exclude that from the instructions because then you get issue like this thread asking for clarification.

That's why.

[ssl]

That's why.

Each CDB extension has its own support section to discuss a problem with a translation.
Extensions have been included in phpBB since version 3.1 and are in no way mandatory for the proper functioning of a phpBB board

[wfarrell]

I am not talking about extensions. I am talking about languages.

Each language file for 3.3.x contains 3 folders (not 2 as described in the official phpBB documentation): /ext, /styles, and /language. The instructions mention only the need to upload the /styles and /language folders, and ignore the need to upload /ext (which contains data for the default/standard viglink extension.

That should be corrected, otherwise the user may neglect to upload /ext to the server, leaving the viglink extension without support for that language. Or the user may be confused by this error in the instructions, as I was.

It is obvious that a child style of prosilver will inherit the parameters of prosilver, so it is not useful to copy a folder into the child style.

Thank you. I thought that was probably the case, but that inheritance is not well explained (in anything I've found), and according to the official instructions it is required for all styles except prosilver and subsilver2. You have confirmed that it is not required for all other styles, which means the instructions are incorrect and should be fixed.