Bug: blade files cannot be localized (Sage 10-beta.2)

[SergiArias]

Terms

• I have read the guidelines for Contributing to Roots Projects
• This request is not a duplicate of an existing issue
• I have read the docs and followed them (if applicable)
• I have seached the Roots Discourse for answers and followed them (if applicable)
• This is not a personal support request that should be posted on the Roots Discourse community

Description

In Sage 10.0.0-beta.1, all blade views were cached as php files in storage folder. Now this is not happening (I am not sure if it's intended). The problem is that I cannot use localization functions like __('Some string', 'sage') as they won't be catched by the pot file generator.

Steps To Reproduce

 <h2>{!! __('Frequently asked questions', 'sage') !!}</h2>

Expected Behavior

The string should be catched by the pot file generator

Actual Behavior

The string is ignored by the pot file generator as it's not inside a php file

Relevant Log Output

No response

Versions

10.0.0-beta-2

[SergiArias]

It's related to this pull request: #2837
Being the views now in wp-content instead of the theme itself, how can we localize strings?

[retlehs]

is this not a dupe of #2672 (comment)? (it seems like paths need to be adjusted?)

can you please update this bug report to be more specific/have more details about the bug? we don't know which commands you're running to generate pot files

[SergiArias]

I am using Loco Translate plugin to both generate the pot file and translate it, and it looks inside the theme files, not the wp-content ones. I will try the method mentioned in 2672 though and update the bug.

[retlehs]

well that definitely makes a difference and absolutely needed to be said earlier haha

i don't think it's reasonable to expect a wordpress plugin to generate a pot file for a theme that's using blade. please followup in #2672 if you have issues with using wp-cli to generate a pot file