Can you include a screenshot of the pages on your development site after the translations have been applied? That would show us that you successfully tested it and that the work is correct.
Before:

After:

I'm not sure we want to combine the first three paragraphs just to save a few translation keys. At least not without edits to make the sentence flow less abrupt. As a native English speaker, I could make those edits.

But I'd much prefer to use the original text in three separate paragraphs.

I'm not sure we want to combine the first three paragraphs just to save a few translation keys. At least not without edits to make the sentence flow less abrupt. As a native English speaker, I could make those edits.

But I'd much prefer to use the original text in three separate paragraphs.

If so, if you want to combine them in one go, they cannot go down the line. See for example: https://lichess.org/faq#timeout, https://github.com/lichess-org/lila/blob/master/app/views/site/faq.scala#L155, https://github.com/lichess-org/lila/blob/master/translation/source/faq.xml#L51

Question for M-DinhHoangViet - is your given name Hoang or Viet? What's the best way to address you that's shorter than 15 characters?

Question for M-DinhHoangViet - is your given name Hoang or Viet? What's the best way to address you that's shorter than 15 characters?

Many people mistake my name as Dinh, and some mistake my name as Hoang. But actually my name is Viet

Hello Viet, I was referring to the first three paragraphs:

Paragraph 1:
            Most browsers can prevent sound from playing on a freshly loaded page to protect users. 
            Imagine if every website could immediately bombard you with audio ads.

Paragraph 2:
            The red mute icon appears when your browser prevents lichess.org from playing a sound.
            Usually this restriction is lifted once you click something. On some mobile browsers,
            touch dragging a piece does not count as a click. In that case you must tap the board to
            allow sound at the start of each game.

Paragraph 3:
            We show the red icon to alert you when this happens. Often you can explicitly allow
            lichess.org to play sounds. Here are instructions for doing so on recent versions of
            some popular browsers.

I understand that there is no obvious way to place paragraph breaks within a single translation. But for this text, when the paragraphs are combined at the view layer, the resulting text becomes harder to read and understand. So I'm wondering if we should treat each paragraph as its own translation so they can be rendered individually.

  p(mostBrowsersCanPreventSound()),
  p(theRedMuteIcon()),
  p(hereAreInstructions())

I want the same as you, but what about the opinions of @ornicar and @fitztrev

Apparently there is a function that can help us here.
Add import lila.common.String.html.nl2br near the other imports at the top of app/views/site/faq.scala
then you can do:

  p(nl2br(allThreeParagraphs())) // note to Viet - choose a better i18n key name :)

nl2br will parse the translation text and replace newlines with <br> which will separate the paragraphs.

Apparently there is a function that can help us here. Add import lila.common.String.html.nl2br near the other imports at the top of app/views/site/faq.scala then you can do:

  p(nl2br(allThreeParagraphs())) // note to Viet - choose a better i18n key name :)

nl2br will parse the translation text and replace newlines with <br> which will separate the paragraphs.

it not working

Try this line instead:

p(nl2br(enableAutoplayForSoundsA.txt())),

@M-DinhHoangViet To fix the build now you can run these 2 commands in gitpod in the terminal.

cd /workspace/lila-docker
./lila-docker format

That will fix the tab and space combination issue. Then you can commit the change.

done!

Well done everyone, that's a wrap