Click the links to see the different scenarios
Since imagery is a visual representation of a company's brand/property, all images are located in the brand directory within the root image directory of the site. Managing brand images with this approach, there likely would be no need for an images directory at the root level.
The logo, in theory, may not be language dependent but is brand dependent. The image reference would reside in an external stylesheet located at [HTTP(S)][domain]/styles/[brand]/design.css The file location of the logo within that stylesheet would be /images/sony/logo_mt120_2.gif
This section contains 2 background images: 1 as an inline style to the <p>, the other as a background image of the <div> sourced by an external stylesheet.
The inline style image path is /images/[brand]/[language]/inline.png, however, in practice could be coded: <%=gsHTTP %>/images/<%=coBrand %><%=language %>inline.png
The external stylesheet path is [HTTP(S)][domain]/styles/[brand]/[language]/design.css with an image path of /images/[brand]/[language]/external.png, however, in practice would be coded: <%=gsHTTP %>/styles/<%=coBrand %>/<%=language %>/design.css and /images/[brand]/[language]/external.png, respectively.
This approach will work but creates additional, duplicative work whenever a new cobrand or language is introduced and creates confusion within the URL structure.
When a new cobrand is introduced, one must copy and paste no fewer than 2 directories for each cobrand. For each directory at the root level that contains a cobrand, i.e.: images and styles; one would duplicate and rename that directory. When a new language is introduced, one would have to create twice as many language directories than if the alternate approach were used, i.e.: images/movietickets/fr, images/sony/fr, styles/movietickets/fr, styles/sony/fr. After this duplication is complete, one needs to go into the stylesheet and perform a find and replace on the cobrand name and the language - a task not required in the alternate method.
Confusion is created with this approach as one must memorize how URL strings are built since the URL is broken into multiple dynamic and static references. Granted, the variables that build the URL could be fully built up so that a single variable is needed, but this approach then requires twice as many variables as the other as the static images and static styles directories must now be accounted for dynamically whereas in the alternate approach, they can basically be ignored as they are static 100% of the time.
Lastly, one might thing the duplicative work mentioned above could be eliminated by simply moving the language directories up one level to be direct children of the images and styles directory. Yes, it is true the workload would be cut in half, but now you would no longer have the facility to load unique images and stylsheets based on cobrand or languages.