GlotPress

Translation of Breakdance & Oxygen: Turkish

Filter ↓ • Sort ↓ • All (6,286) • Translated (5,668) • Untranslated (618) • Waiting (0) • Fuzzy (0) • Warnings (4) • Current Filter (1)
← 1 →
Prio Original string Translation —
Imports a raw CSS stylesheet into the %1$s global CSS selectors. Each rule is routed to a selector: a single class (.btn) becomes a "class" selector; a class plus a pseudo-state/combinator (.card:hover, .card .card-image) becomes a nested child; anything else (comma lists, id/tag selectors) becomes a verbatim "custom" selector. `@media` blocks whose query exactly matches a registered breakpoint are imported into that breakpoint (call get-breakpoints first); `:root { --x: y }` declares global CSS variables. Naming a Google Font first in a font-family declaration or :root variable value loads the webfont automatically (no @font-face/@import/link needed), so use real fonts instead of system-stack workarounds. A rule REPLACES the matched selector's properties at the breakpoint it targets (it does not merge onto the stored ones); breakpoints the stylesheet does not restyle keep their stored properties, so importing only a @media rule updates that breakpoint without touching base properties. EDITING AN EXISTING SELECTOR: because of that replacement, this is not a patch tool: a rule carrying only the declaration you want to change deletes every other declaration that breakpoint held. Read the selector back first with get-css-selectors (include_properties: true) and re-import its complete rule, including its @media rules, with the change folded in. Any properties an import did drop this way are named in the response's "warnings". RULES: prefer flat single-class selectors and parent-state+named-child nesting; avoid bare tag selectors and id selectors. A rule starting with a class is stored as one nested child under that class with its whole descendant chain, so keep chains short for your own markup and write the full chain only to out-specify an existing stylesheet (WooCommerce, the builder's element CSS). Never import a tag-level reset: enable the builder's Modern Normalize stylesheet instead, with set-settings ({"advanced": {"modern_normalize_enabled": true}}). If you prefix new class names, use the site's class prefix (the "css_prefix" returned by get-css-selectors and site-info) instead of inventing one, so all agents on this site share a convention. Before adding layout CSS to an element, call get-element-schemas first: many elements have native design properties that must be used instead. You have to log in to add a translation. Details

Imports a raw CSS stylesheet into the %1$s global CSS selectors. Each rule is routed to a selector: a single class (.btn) becomes a "class" selector; a class plus a pseudo-state/combinator (.card:hover, .card .card-image) becomes a nested child; anything else (comma lists, id/tag selectors) becomes a verbatim "custom" selector. `@media` blocks whose query exactly matches a registered breakpoint are imported into that breakpoint (call get-breakpoints first); `:root { --x: y }` declares global CSS variables. Naming a Google Font first in a font-family declaration or :root variable value loads the webfont automatically (no @font-face/@import/link needed), so use real fonts instead of system-stack workarounds. A rule REPLACES the matched selector's properties at the breakpoint it targets (it does not merge onto the stored ones); breakpoints the stylesheet does not restyle keep their stored properties, so importing only a @media rule updates that breakpoint without touching base properties. EDITING AN EXISTING SELECTOR: because of that replacement, this is not a patch tool: a rule carrying only the declaration you want to change deletes every other declaration that breakpoint held. Read the selector back first with get-css-selectors (include_properties: true) and re-import its complete rule, including its @media rules, with the change folded in. Any properties an import did drop this way are named in the response's "warnings". RULES: prefer flat single-class selectors and parent-state+named-child nesting; avoid bare tag selectors and id selectors. A rule starting with a class is stored as one nested child under that class with its whole descendant chain, so keep chains short for your own markup and write the full chain only to out-specify an existing stylesheet (WooCommerce, the builder's element CSS). Never import a tag-level reset: enable the builder's Modern Normalize stylesheet instead, with set-settings ({"advanced": {"modern_normalize_enabled": true}}). If you prefix new class names, use the site's class prefix (the "css_prefix" returned by get-css-selectors and site-info) instead of inventing one, so all agents on this site share a convention. Before adding layout CSS to an element, call get-element-schemas first: many elements have native design properties that must be used instead.

You have to log in to edit this translation.

Meta

Status:
untranslated
Comment:
translators: %s: builder name (Breakdance or Oxygen).
References:
Priority:
normal
More links:
Legend:
Current
Waiting
Rejected
Fuzzy
Old
With warnings
← 1 →

Export as • Download Translation Package (Updated 3 weeks ago)