>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3570518. --> Reported by: [stefan.korn](https://www.drupal.org/user/1942204) Related to !48 !47 >>> <h3>Problem/Motivation</h3> <p>The <code>_potx_find_language_names()</code> function fails to parse LanguageManager.php in Drupal 11 due to PHP array syntax changes.</p> <p>Drupal 11's LanguageManager.php uses modern short array syntax:</p> <pre> public static function getStandardLanguageList() { return [ 'af' =&gt; ['Afrikaans', 'Afrikaans'], // ... ]; } </pre><p>But potx's parsing logic only handles old array syntax:</p> <pre> public static function getStandardLanguageList() { return array( 'af' =&gt; array('Afrikaans', 'Afrikaans'), // ... ); } </pre><p>The parser looks for <code>T_ARRAY</code> tokens which are only generated by <code>array()</code> syntax. The modern short array syntax <code>[]</code> uses character tokens (<code>[</code><br> and <code>]</code>) instead, causing the parser to fail extracting language names.</p> <h3>Proposed resolution</h3> <p>Update <code>_potx_find_language_names()</code> to handle both array syntaxes by:</p> <ol> <li>Looking for <code>T_DOUBLE_ARROW</code> (<code>=&amp;gt;</code>) tokens to locate each language's inner array</li> <li>Detecting whether the inner array uses <code>T_ARRAY</code> (old syntax) or <code>[</code> character (new syntax)</li> <li>Extracting language names from both <code>array(...)</code> and <code>[...]</code> structures</li> </ol> <p>On the 7.x-3.x branch, also extract <code>_potx_parse_php_file()</code> as a separate function from <code>_potx_process_file()</code> to enable direct testing of PHP parsing logic without<br> duplicating tokenization code in tests.</p> <h3>Remaining tasks</h3> <p>None.</p> <h3>User interface changes</h3> <p>None.</p> <h3>API changes</h3> <p><strong>7.x-3.x only:</strong> New function <code>_potx_parse_php_file()</code> extracted from <code>_potx_process_file()</code>. This is an internal API function for parsing PHP code.</p> <h3>Data model changes</h3> <p>None.</p> <h3>AI usage</h3> <p>AI assistance was used to generate this issue summary and to generate the fixes. Claude Code Soonet 4.5 to be more precise.</p>