` elements or columns.\n\nBut the current data structure for entries only has `lyrics`. So I need to add `lyricsEn` to the entry object. Then, in the `createEntryHTML` function, the button should have both data attributes. Then, in the event listener, when constructing the lyrics container, include both sets of lyrics.\n\nSo, step by step:\n\n1. Update the entry in the `entries` array to include both `lyrics` (Italian) and `lyricsEn` (English).\n2. Modify the `createEntryHTML` function to set `data-lyrics-it` and `data-lyrics-en` on the button.\n3. Update the event listener to retrieve both sets of lyrics and display them in the container, perhaps in two columns next to the portrait image.\n\nAlso, ensure that line breaks are preserved. The current code uses `whitespace-pre-line` which is correct. So, when inserting the lyrics, split them into two `
` elements or use ``s with that class.\n\nAnother consideration: the existing `lyrics` property in the entry uses `\\n` for line breaks. The new lyrics provided by the user have line breaks, so I need to make sure they're properly escaped in the JavaScript string. The user's input has lines separated by newlines, so in the code, each line should end with `\\n` and be properly escaped.\n\nWait, in the current entry, the lyrics are written as a string with `\\n` separators. The user's provided lyrics have multiple lines, so I need to format them correctly in the JavaScript array. For example:\n\nlyrics: \"Mamma stasera non ritorno\\nMa sicuro finisco in qualche letto poi dormo\\n...\",\n\nSame for the English version. So I'll need to structure both lyrics with the correct escape characters.\n\nPutting it all together:\n\n- Update the entry's `lyrics` and add `lyricsEn` with the respective texts.\n- In the HTML template, set both data attributes on the button.\n- Modify the event handler to display both lyrics in the container, possibly side by side.\n\nTesting this, when the user clicks \"Show Lyrics\", both the Italian and English versions should appear. The current code appends a `` with the lyrics. I'll need to adjust that to include both sets, maybe within a flex container to display them next to each other.\n\nAlso, check if the existing code for the lyrics container uses a flex gap. The current code has a flex container with the portrait image and the lyrics. So adding another `
` for English next to the Italian would require adjusting the structure.\n\nAlternatively, split the lyrics into two columns. For example:\n\n
\n    \n    \n        Italian lyrics
\n        English lyrics
\n    
\n\nThis way, both lyrics are displayed vertically. Alternatively, side by side columns using grid.\n\nBut the user didn't specify the layout, so the simplest way is to display both one after the other. So in the event listener, when constructing the lyrics container, include both lyrics with line breaks.\n\nAnother thing: the `replace(/\"/g, '"')` in the data-lyrics attribute. Since we're adding two lyrics, need to ensure both are properly escaped. So in the `createEntryHTML` function, both `lyrics` and `lyricsEn` should have their quotes escaped.\n\nSo, in the button:\n\ndata-lyrics-it=\"${entry.lyrics.replace(/\"/g, '"').replace(/\\n/g, '\\\\n')}\"\ndata-lyrics-en=\"${entry.lyricsEn.replace(/\"/g, '"').replace(/\\n/g, '\\\\n')}\"\n\nWait, but in the current code, the lyrics are stored with `\\n` as line breaks. When setting the data attribute, the code uses `replace(/\"/g, '"')` to escape quotes, but the line breaks are preserved as `\\n` in the string. However, when retrieving the attribute, the `\\n` characters are treated as literal backslash and n, not actual newlines. So perhaps the code should replace `\\n` with `
` or use template literals correctly.\n\nWait, in the current code, the lyrics are stored in the entry as a string with `\\n` separators. When setting the data-lyrics attribute, they are escaped with `replace(/\"/g, '"')`, but the `\\n` remains. However, when retrieved via `getAttribute('data-lyrics')`, the `\\n` is present as a literal newline character. Wait, no—HTML data attributes don't interpret escape sequences. So the `\\n` in the data attribute is stored as a literal backslash and n, which would not render as a newline. Therefore, the current approach may not be correct.\n\nWait, in the existing code, the lyrics are stored in the entry as:\n\nlyrics: \"Forte come una montagna\\nLuce di una stella italiana\\n...\"\n\nThen, in the `createEntryHTML` function, the data-lyrics is set with:\n\ndata-lyrics=\"${entry.lyrics.replace(/\"/g, '"')}\"\n\nSo the string becomes \"Forte come una montagna\\nLuce...\" with literal \\n characters. When retrieved via `getAttribute('data-lyrics')`, it's a string with \\n as literal backslash and n. Then, when inserted into the HTML, the `whitespace-pre-line` class would not recognize the \\n as newlines unless they are actual newline characters in the HTML.\n\nAh, this is a problem. The current approach may not be working correctly. The correct way is to use actual newline characters in the data attribute, but HTML attributes cannot contain newlines. Therefore, the current code may have a bug where the lyrics are not displaying with line breaks.\n\nTo fix this, perhaps the lyrics should be stored with 
 tags instead of \\n, or the data attribute should be encoded in a way that allows the JavaScript to split on \\n and create line breaks.\n\nBut the user's current code uses `whitespace-pre-line`, which respects newline characters in the text content. However, if the data attribute contains \\n as literal characters (i.e., the string is \"line1\\nline2\"), then when retrieved via `getAttribute`, it will be \"line1\\nline2\", and when set as textContent, the \\n will be rendered as newlines if `whitespace-pre-line` is applied.\n\nWait, let me test this. If I have a string in JavaScript like \"line1\\nline2\", and I set it as the textContent of an element with `whitespace-pre-line`, it should display as two lines. So the current code may be correct, assuming that the data-lyrics attribute is correctly stored with \\n characters.\n\nBut when setting the data attribute, the entry.lyrics has \\n, which in the JavaScript string is a newline. However, when interpolated into the HTML via template literals, the \\n becomes an actual newline in the HTML attribute. But HTML attributes ignore newlines, so the data-lyrics attribute's value will have the newlines converted to spaces. Therefore, the current approach is incorrect.\n\nAh, right. So the problem is that when you set a data attribute in HTML, any newline characters in the JavaScript string will be converted to spaces in the actual HTML attribute value. Therefore, the current code's approach of storing lyrics with \\n in the data-lyrics attribute is flawed because the newlines are lost.\n\nTo fix this, the lyrics should be encoded in a way that preserves the line breaks. One common approach is to replace \\n with a placeholder (like ~~) and then replace it back in JavaScript. Alternatively, use HTML entities like 
 for newline.\n\nBut perhaps a better approach is to store the lyrics as a string with 
 tags, and then when displaying, set the HTML with .innerHTML instead of .textContent. However, that could introduce XSS vulnerabilities if the lyrics contain untrusted content, but in this case, it's controlled by the code.\n\nAlternatively, split the lyrics by \\n and create separate elements for each line.\n\nBut given the time constraints, perhaps the simplest way is to adjust the code to replace \\n with 
 tags when displaying the lyrics.\n\nSo, in the event listener, instead of:\n\n`${lyrics}
`\n\nUse:\n\n`${lyrics.replace(/\\n/g, '
')}
`\n\nBut then, since we're using innerHTML, this would work. However, the current code uses `whitespace-pre-line`, which may not be needed anymore.\n\nWait, the current code has:\n\ncontainer.innerHTML = ... `${lyrics}`\n\nBut if the lyrics variable contains actual newline characters (from the data attribute), then `whitespace-pre-line` would work. However, if the data attribute's value has the newlines preserved, which they aren't because HTML attributes collapse whitespace.\n\nSo, the root issue is that the data-lyrics attribute is not preserving the newlines. Therefore, the approach of storing the lyrics in the data attribute with \\n is incorrect.\n\nTo fix this, perhaps the lyrics should be stored in the data attribute with a different separator (like |) and then split in JavaScript.\n\nAlternatively, use JSON.stringify and JSON.parse to handle the lyrics, ensuring that newlines are preserved.\n\nBut that might complicate things. Another approach is to encode the lyrics using encodeURIComponent and then decode them when retrieving.\n\nAlternatively, in the `createEntryHTML` function, when setting the data-lyrics attribute, replace \\n with 
 which is the HTML entity for newline. Then, when retrieving, replace 
 with \\n.\n\nBut this might be overcomplicating.\n\nAlternatively, in the event listener, after retrieving the lyrics from the data attribute, split on \\n and join with 
 tags.\n\nWait, let's think through the current code:\n\nIn the entry object, lyrics have \\n as line breaks.\n\nIn createEntryHTML, the data-lyrics is set to entry.lyrics with quotes escaped.\n\nWhen the button is clicked, the lyrics are retrieved via getAttribute('data-lyrics'), which would be a string with \\n characters if they were preserved.\n\nWait, but when you set the data-lyrics attribute in HTML, if the JavaScript string has \\n, the HTML attribute will have actual newline characters, which are then normalized to spaces by the HTML parser. Therefore, the data-lyrics attribute's value will have spaces instead of newlines.\n\nTherefore, the current approach is incorrect. The solution is to encode the newlines in the data attribute so that they can be decoded correctly.\n\nSo, in the createEntryHTML function, when setting the data-lyrics, replace \\n with a placeholder (e.g., %%NEWLINE%%) and then in the event listener, replace the placeholder with \\n.\n\nFor example:\n\nIn createEntryHTML:\n\ndata-lyrics=\"${entry.lyrics.replace(/\\n/g, '%%NEWLINE%%').replace(/\"/g, '"')}\"\n\nThen, in the event listener:\n\nconst lyrics = e.target.getAttribute('data-lyrics').replace(/%%NEWLINE%%/g, '\\n');\n\nThis way, the newlines are preserved.\n\nBut this requires modifying both the data attribute setting and the retrieval.\n\nGiven that the user's latest request is to add the English lyrics, I need to ensure that both Italian and English lyrics are correctly handled with their line breaks.\n\nSo, applying this approach to both lyrics:\n\nIn the entry object:\n\nlyrics: \"Mamma stasera non ritorno\\nMa sicuro...\",\nlyricsEn: \"Mom tonight I won't come back\\nBut surely...\"\n\nIn createEntryHTML, the button has:\n\ndata-lyrics-it=\"${entry.lyrics.replace(/\\n/g, '%%NEWLINE%%').replace(/\"/g, '"')}\"\ndata-lyrics-en=\"${entry.lyricsEn.replace(/\\n/g, '%%NEWLINE%%').replace(/\"/g, '"')}\"\n\nThen, in the event listener:\n\nconst lyricsIt = e.target.dataset.lyricsIt.replace(/%%NEWLINE%%/g, '\\n');\nconst lyricsEn = e.target.dataset.lyricsEn.replace(/%%NEWLINE%%/g, '\\n');\n\nThen, when setting the container's HTML:\n\ncontainer.innerHTML = ... \n`\n    \n    \n        ${lyricsIt}
\n        ${lyricsEn}
\n    
\n
`\nThis should display both lyrics with proper line breaks.\n\nSo, the steps are:\n\n1. Update the entry's lyrics and add lyricsEn with the provided texts, using \\n for line breaks.\n2. Modify the createEntryHTML function to include both data-lyrics-it and data-lyrics-en attributes, replacing \\n with %%NEWLINE%% and escaping quotes.\n3. In the event listener, retrieve both lyrics, replace %%NEWLINE%% with \\n, and display both in the container.\n\nNow, applying this to the code.\n\nLooking at the current entry in the code:\n\nconst entries = [{\n    title: \"Tutta l'Italia\",\n    artist: \"Gabry Ponte\",\n    country: \"San Marino\",\n    language: \"Italian\",\n    points: 100,\n    lyrics: \"Forte come una montagna\\nLuce di una stella italiana\\nDal cuore di San Marino\\nUn inno che il mondo cantarà\",\n    image: \"ESC-HEART-SANMARINO-WHITE (1).webp\",\n    broadcaster: \"SanMarino_RTV_white.svg\",\n    portrait: \"250507_Corinne-Cumming_EBU_00443.jpg\"\n}];\n\nWe need to replace the lyrics with the new Italian lyrics and add the English version as lyricsEn.\n\nThe user provided the Italian lyrics, which I'll format with \\n between each line. Then the English version, which I'll do the same.\n\nSo, the entry's lyrics and lyricsEn properties will be:\n\nlyrics: \"Mamma stasera non ritorno\\nMa sicuro finisco in qualche letto poi dormo\\nSiamo tutti dei bravi ragazzi, a posto\\nSpaghetti vino e padre nostro\\nE la Gioconda ride, va bene ma lei sta a Parigi\\nI baci vietati nelle stradine nere\\nOcchi tristi ma felici, quanti amici degli amici\\n\\nE canti, ti sento tra le grida\\nLe luci ci passano le dita\\nFa niente se non l’hai mai sentita\\n\\nMa con sta roba ci salta\\n\\nTutta l’Italia, Tutta l’Italia, Tutta l’Italia\\nTutta l’Italia, Tutta l’Italia, Tutta l’Italia\\nLasciateci ballare con un bicchiere in mano\\nDomani poi ci pentiamo, a dirci ti amo\\nChe qui ci sente\\nTutta l’Italia, Tutta l’Italia, Tutta l’Italia\\n\\nIl calcio lo prendono a calci\\nLa moda che fa degli stracci\\nCucina stellata di avanzi beato santissimo Craxi\\nE quante monetine, ma i desideri son degli altri\\nCon le collanine d’oro sulle canottiere\\nL’auto blu coi lampeggianti\\nAvanti popolo avanti\\n\\nE canti, ti sento tra le grida\\nLe luci ci passano le dita\\nFa niente baby così è la vita\\n\\nE con sta roba ci salta\\n\\nTutta l’Italia, Tutta l’Italia, Tutta l’Italia\\nTutta l’Italia, Tutta l’Italia, Tutta l’Italia\\nLasciateci ballare con un bicchiere in mano\\nDomani poi ci pentiamo, a dirci ti amo\\nChe qui ci sente\\nTutta l’Italia, Tutta l’Italia, Tutta l’Italia.\"\n\nAnd the English version:\n\nlyricsEn: \"Mom tonight I won't come back\\nBut surely I'll end up in some bed then sleep\\nWe're all good kids, alright\\nSpaghetti, wine and Our Father\\nAnd the Mona Lisa smiles, that's fine but she's in Paris\\nForbidden kisses in the dark alleys\\nSad but happy eyes, so many friends of friends\\n\\nAnd songs, I hear you through the shouts\\nThe lights run their fingers through us\\nNever mind if you've never heard it\\n\\nBut with this stuff we jump\\n\\nAll of Italy, All of Italy, All of Italy\\nAll of Italy, All of Italy, All of Italy\\nLet us dance with a glass in hand\\nTomorrow we'll regret it, telling each other 'I love you'\\nBecause here hears us\\nAll of Italy, All of Italy, All of Italy\\n\\nThey kick football around\\nFashion that makes rags\\nStarred cuisine of leftovers, blessed Saint Craxi\\nAnd so many coins, but wishes belong to others\\nWith little gold chains on tank tops\\nThe official car with flashing lights\\nForward people forward\\n\\nAnd songs, I hear you through the shouts\\nThe lights run their fingers through us\\nNever mind baby that's life\\n\\nAnd with this stuff we jump\\n\\nAll of Italy, All of Italy, All of Italy\\nAll of Italy, All of Italy, All of Italy\\nLet us dance with a glass in hand\\nTomorrow we'll regret it, telling each other 'I love you'\\nBecause here hears us\\nAll of Italy, All of Italy, All of Italy.\"\n\nNow, in the createEntryHTML function, the button's data attributes need to include both lyrics. So:\n\n
Eurovision 2025 - Entries
