wikimedia/mediawiki-extensions-Cite
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/Cite synced 2024-11-24 06:54:00 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-Cite/modules/parsoid-styles/ext.cite.style.ar.css

24 lines
518 B
CSS
Raw Normal View History

Parsoid CSS: Add (script-generated) language-specific counters * These files were generated with the script in I3623e42d4cad7975813892a8f0f7765b74a638c5 * These styles mimic the behavior of Language::formatNumNoSeparators and Language::localizeSeparators used by a couple of methods. ReferencesFormatter:referencesFormatEntryNumericBacklinkLabel calls ReferenceMessageLocalizer::localizeDigits which calls that core Language method. FootnoteMarkFormatter::linkRef calls localizeDigits as well. - '.reference a*' CSS rules mimic linkRef localization - 'span[rel="mw:referencedBy" ]*' rule mimics localization of referencesFormatEntryNumericBacklinkLabel * Overrode all hand-crafted language CSS files from previous patches. The content of some of those hand-crafted CSS files will end up in those wikipedia's Common.css -- specifically for es, fr, sv wikipedias. sv and es have non-canonical formatting strings that aren't handled by the script right now and so leaving them behind. I need to look at fr output more carefully, so leaving that behind as well. But the generated ones are more accurate when combined with the wiki-specific CSS files genreated by the other script that processes site messages. * Some files could potentially be removed by looking at language fallback chains, but the redundancy is not a problem for now. * Tweak the resource loader script to use "_" instead of "-" when looking for a resource file. Bug: T156350 Change-Id: I000b4538bf2be681b85df5813efed083458a4281
2022-11-04 03:28:38 +00:00
/* @noflip */
.mw-cite-dir-ltr {
direction: ltr;
text-align: left;
}
/* @noflip */
.mw-cite-dir-rtl {
direction: rtl;
text-align: right;
}
Wire subref counting into the numbering renderer Significant change is that footnote marker numbers are changed from being a CSS-rendered marker to using the rendered "fallback" text. This could be avoided using the same trick as is implemented for the reflist: send an inline style variable with the marker content; but let's only do this if really necessary for user experience. Template-produced refs are still wrong, but this patch continues to render them as they come from Parsoid, in the content script. TODO in later patches: * reuse of a subref is rendered as '3.2.1' in reader view but '3.0' and '3.1' in the editor. * subref numbering is backwards in RTL languages Bug: T247921 Change-Id: Ieff73769f8ebbc3724f6a9b498487c4e7d09aa2e
2024-06-28 10:12:37 +00:00
.mw-ref > a[ style~='mw-Ref' ]::after {
Parsoid CSS: Add (script-generated) language-specific counters * These files were generated with the script in I3623e42d4cad7975813892a8f0f7765b74a638c5 * These styles mimic the behavior of Language::formatNumNoSeparators and Language::localizeSeparators used by a couple of methods. ReferencesFormatter:referencesFormatEntryNumericBacklinkLabel calls ReferenceMessageLocalizer::localizeDigits which calls that core Language method. FootnoteMarkFormatter::linkRef calls localizeDigits as well. - '.reference a*' CSS rules mimic linkRef localization - 'span[rel="mw:referencedBy" ]*' rule mimics localization of referencesFormatEntryNumericBacklinkLabel * Overrode all hand-crafted language CSS files from previous patches. The content of some of those hand-crafted CSS files will end up in those wikipedia's Common.css -- specifically for es, fr, sv wikipedias. sv and es have non-canonical formatting strings that aren't handled by the script right now and so leaving them behind. I need to look at fr output more carefully, so leaving that behind as well. But the generated ones are more accurate when combined with the wiki-specific CSS files genreated by the other script that processes site messages. * Some files could potentially be removed by looking at language fallback chains, but the redundancy is not a problem for now. * Tweak the resource loader script to use "_" instead of "-" when looking for a resource file. Bug: T156350 Change-Id: I000b4538bf2be681b85df5813efed083458a4281
2022-11-04 03:28:38 +00:00
content: '[' counter( mw-Ref, arabic-indic ) ']';
}
Wire subref counting into the numbering renderer Significant change is that footnote marker numbers are changed from being a CSS-rendered marker to using the rendered "fallback" text. This could be avoided using the same trick as is implemented for the reflist: send an inline style variable with the marker content; but let's only do this if really necessary for user experience. Template-produced refs are still wrong, but this patch continues to render them as they come from Parsoid, in the content script. TODO in later patches: * reuse of a subref is rendered as '3.2.1' in reader view but '3.0' and '3.1' in the editor. * subref numbering is backwards in RTL languages Bug: T247921 Change-Id: Ieff73769f8ebbc3724f6a9b498487c4e7d09aa2e
2024-06-28 10:12:37 +00:00
.mw-ref > a[ style~='mw-Ref' ][ data-mw-group ]::after {
Parsoid CSS: Add (script-generated) language-specific counters * These files were generated with the script in I3623e42d4cad7975813892a8f0f7765b74a638c5 * These styles mimic the behavior of Language::formatNumNoSeparators and Language::localizeSeparators used by a couple of methods. ReferencesFormatter:referencesFormatEntryNumericBacklinkLabel calls ReferenceMessageLocalizer::localizeDigits which calls that core Language method. FootnoteMarkFormatter::linkRef calls localizeDigits as well. - '.reference a*' CSS rules mimic linkRef localization - 'span[rel="mw:referencedBy" ]*' rule mimics localization of referencesFormatEntryNumericBacklinkLabel * Overrode all hand-crafted language CSS files from previous patches. The content of some of those hand-crafted CSS files will end up in those wikipedia's Common.css -- specifically for es, fr, sv wikipedias. sv and es have non-canonical formatting strings that aren't handled by the script right now and so leaving them behind. I need to look at fr output more carefully, so leaving that behind as well. But the generated ones are more accurate when combined with the wiki-specific CSS files genreated by the other script that processes site messages. * Some files could potentially be removed by looking at language fallback chains, but the redundancy is not a problem for now. * Tweak the resource loader script to use "_" instead of "-" when looking for a resource file. Bug: T156350 Change-Id: I000b4538bf2be681b85df5813efed083458a4281
2022-11-04 03:28:38 +00:00
content: '[' attr( data-mw-group ) ' ' counter( mw-Ref, arabic-indic ) ']';
}
Use double-colon for pseudo-elements * Linting rule has been fixed to accept these now. Change-Id: I51d866ec18c9e1d675f43b3c60f3ad874bba041e
2023-02-15 15:06:40 +00:00
span[ rel='mw:referencedBy' ] > a::before {
Parsoid CSS: Add (script-generated) language-specific counters * These files were generated with the script in I3623e42d4cad7975813892a8f0f7765b74a638c5 * These styles mimic the behavior of Language::formatNumNoSeparators and Language::localizeSeparators used by a couple of methods. ReferencesFormatter:referencesFormatEntryNumericBacklinkLabel calls ReferenceMessageLocalizer::localizeDigits which calls that core Language method. FootnoteMarkFormatter::linkRef calls localizeDigits as well. - '.reference a*' CSS rules mimic linkRef localization - 'span[rel="mw:referencedBy" ]*' rule mimics localization of referencesFormatEntryNumericBacklinkLabel * Overrode all hand-crafted language CSS files from previous patches. The content of some of those hand-crafted CSS files will end up in those wikipedia's Common.css -- specifically for es, fr, sv wikipedias. sv and es have non-canonical formatting strings that aren't handled by the script right now and so leaving them behind. I need to look at fr output more carefully, so leaving that behind as well. But the generated ones are more accurate when combined with the wiki-specific CSS files genreated by the other script that processes site messages. * Some files could potentially be removed by looking at language fallback chains, but the redundancy is not a problem for now. * Tweak the resource loader script to use "_" instead of "-" when looking for a resource file. Bug: T156350 Change-Id: I000b4538bf2be681b85df5813efed083458a4281
2022-11-04 03:28:38 +00:00
content: counter( mw-references, arabic-indic ) '٫' counter( mw-ref-linkback, arabic-indic );
}
Reference in a new issue Copy permalink