GlotPress

Translation of Ultimate Multisite: Domain Seller: Spanish (Spain)

Filter ↓ Sort ↓ All (694) Translated (679) Untranslated (0) Waiting (15) Fuzzy (0) Warnings (11)
1
Prio Original string Translation
Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price. First, the user has given a text to translate: "Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price." I need to translate this from English to Spanish (Spain), using informal "tú" form. But note: the text is instructional or descriptive, so the "tú" form might not directly apply here since it's not addressing someone directly. However, the instruction says "Use informal 'tú' (not 'usted')", so I should ensure that any implied verbs or pronouns are in the informal form if applicable. The text is: "Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price." Breaking it down: - "Added on top of the provider cost." – This is a phrase, not a full sentence. It might be part of a larger context, but I'll translate it as given. - "E.g." – This is an abbreviation for "for example", which in Spanish is "p.ej." or "por ejemplo". I should use "por ejemplo" since it's more common in natural language. - "20% on a $10 domain = $12 customer price." – This is an example calculation. Now, translating: - "Added on top of the provider cost." – In Spanish, this could be "Añadido sobre el costo del proveedor." But since it's informal, I might use "añadido" which is the past participle, and it doesn't have a subject, so "tú" form isn't directly applied. However, if I were to make it a sentence, like "You add it on top...", but the source is passive. I should keep the structure similar. The instruction says: "Use informal 'tú' (not 'usted')", but in this text, there's no direct verb addressing someone. So, I'll translate literally and ensure that if there's any implied instruction, it's in informal form. Perhaps the context is from a plugin where instructions are given to the user, so I should use informal tone. Let me translate: - "Added on top of the provider cost." – "Añadido sobre el costo del proveedor." But to make it informal, if it's an instruction, it might be "Añade sobre el costo del proveedor." However, the source is "Added", which is past participle, indicating a state. I think "Añadido" is fine. The user said: "Translating a WordPress plugin." So, it might be UI text or description. I should use natural language. Another way: "Se añade sobre el costo del proveedor." But "se" is impersonal, not informal "tú". To use informal "tú", I could say "Añades sobre el costo del proveedor." but that changes the meaning to "You add on top of the provider cost." I need to preserve the meaning. The source is passive or descriptive. Let's look at the full text. The entire text: "Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price." In context, it might be explaining how a markup is applied. So, "Added" might mean "It is added" or "This is added". To use informal "tú", I could translate as if addressing the user: "Añade esto sobre el costo del proveedor." But that adds words. I should stick to the source as much as possible. The instruction says: "Return ONLY the translated text. Use natural language." Perhaps for "Added", I can use "Añadido" which is neutral. Now, glossary term: "customer" = "cliente". So in "customer price", I should use "precio para el cliente" or simply "precio del cliente". The example: "20% on a $10 domain = $12 customer price." – "20% sobre un dominio de $10 = $12 precio del cliente." But in Spanish, we might say "precio para el cliente" or "precio al cliente". To make it informal, I can use "precio del cliente" which is standard. Now, putting it all together: - "Added on top of the provider cost." – "Añadido sobre el costo del proveedor." - "E.g." – "Por ejemplo," - "20% on a $10 domain = $12 customer price." – "20% sobre un dominio de $10 = $12 precio del cliente." But in the example, it's showing a calculation: 20% markup on $10 makes $12. So, "20% sobre un dominio de $10 resulta en $12 precio del cliente." But the source Details

Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price.

Warning: Lengths of source and translation differ too much.
First, the user has given a text to translate: "Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price." I need to translate this from English to Spanish (Spain), using informal "tú" form. But note: the text is instructional or descriptive, so the "tú" form might not directly apply here since it's not addressing someone directly. However, the instruction says "Use informal 'tú' (not 'usted')", so I should ensure that any implied verbs or pronouns are in the informal form if applicable. The text is: "Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price." Breaking it down: - "Added on top of the provider cost." – This is a phrase, not a full sentence. It might be part of a larger context, but I'll translate it as given. - "E.g." – This is an abbreviation for "for example", which in Spanish is "p.ej." or "por ejemplo". I should use "por ejemplo" since it's more common in natural language. - "20% on a $10 domain = $12 customer price." – This is an example calculation. Now, translating: - "Added on top of the provider cost." – In Spanish, this could be "Añadido sobre el costo del proveedor." But since it's informal, I might use "añadido" which is the past participle, and it doesn't have a subject, so "tú" form isn't directly applied. However, if I were to make it a sentence, like "You add it on top...", but the source is passive. I should keep the structure similar. The instruction says: "Use informal 'tú' (not 'usted')", but in this text, there's no direct verb addressing someone. So, I'll translate literally and ensure that if there's any implied instruction, it's in informal form. Perhaps the context is from a plugin where instructions are given to the user, so I should use informal tone. Let me translate: - "Added on top of the provider cost." – "Añadido sobre el costo del proveedor." But to make it informal, if it's an instruction, it might be "Añade sobre el costo del proveedor." However, the source is "Added", which is past participle, indicating a state. I think "Añadido" is fine. The user said: "Translating a WordPress plugin." So, it might be UI text or description. I should use natural language. Another way: "Se añade sobre el costo del proveedor." But "se" is impersonal, not informal "tú". To use informal "tú", I could say "Añades sobre el costo del proveedor." but that changes the meaning to "You add on top of the provider cost." I need to preserve the meaning. The source is passive or descriptive. Let's look at the full text. The entire text: "Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price." In context, it might be explaining how a markup is applied. So, "Added" might mean "It is added" or "This is added". To use informal "tú", I could translate as if addressing the user: "Añade esto sobre el costo del proveedor." But that adds words. I should stick to the source as much as possible. The instruction says: "Return ONLY the translated text. Use natural language." Perhaps for "Added", I can use "Añadido" which is neutral. Now, glossary term: "customer" = "cliente". So in "customer price", I should use "precio para el cliente" or simply "precio del cliente". The example: "20% on a $10 domain = $12 customer price." – "20% sobre un dominio de $10 = $12 precio del cliente." But in Spanish, we might say "precio para el cliente" or "precio al cliente". To make it informal, I can use "precio del cliente" which is standard. Now, putting it all together: - "Added on top of the provider cost." – "Añadido sobre el costo del proveedor." - "E.g." – "Por ejemplo," - "20% on a $10 domain = $12 customer price." – "20% sobre un dominio de $10 = $12 precio del cliente." But in the example, it's showing a calculation: 20% markup on $10 makes $12. So, "20% sobre un dominio de $10 resulta en $12 precio del cliente." But the source
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-04-03 03:18:13
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Disabled desactivado Details

Disabled

Warning: The translation appears to be missing the initial uppercase.
desactivado
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-03-01 15:54:42
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Nameservers servidores DNS Details

Nameservers

Warning: The translation appears to be missing the initial uppercase.
servidores DNS
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-03-01 07:26:26
Date added (local):
Calculating...
References:
Priority:
normal
More links:
  • Singular:
    %d year
  • Plural:
    %d years
  • Singular:
    %d año
  • Plural:
    %d años
Details

Singular:
%d year

%d año
You have to log in to edit this translation.

Plural:
%d years

%d años
You have to log in to edit this translation.

Meta

Status:
waiting
Comment:
translators: %d: number of years for domain registration
Date added (GMT):
2026-02-19 18:44:49
Date added (local):
Calculating...
References:
Priority:
normal
More links:
first year primer año Details

first year

Warning: The translation appears to be missing 1 space at the beginning.
primer año
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-02-22 07:27:24
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Renews at Renueva a Details

Renews at

Warning: The translation appears to be missing 1 space at the end.
Renueva a
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-02-22 07:28:26
Date added (local):
Calculating...
References:
Priority:
normal
More links:
DNS records updated successfully registros DNS actualizados correctamente Details

DNS records updated successfully

Warning: The translation appears to be missing the initial uppercase.
registros DNS actualizados correctamente
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-02-28 21:06:30
Date added (local):
Calculating...
References:
Priority:
normal
More links:
  • Singular:
    Successfully synced %d TLD.
  • Plural:
    Successfully synced %d TLDs.
  • Singular:
    Correctamente sincronizado %d TLD.
  • Plural:
    Correctamente sincronizados %d TLDs.
Details

Singular:
Successfully synced %d TLD.

Correctamente sincronizado %d TLD.
You have to log in to edit this translation.

Plural:
Successfully synced %d TLDs.

Correctamente sincronizados %d TLDs.
You have to log in to edit this translation.

Meta

Status:
waiting
Comment:
translators: %d: number of TLDs synced
Date added (GMT):
2026-03-01 01:55:29
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Settings ajustes Details

Settings

Warning: The translation appears to be missing the initial uppercase.
ajustes
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-03-01 02:55:52
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Customer cliente Details

Customer

Warning: The translation appears to be missing the initial uppercase.
cliente
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-03-01 05:46:30
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Cancel Ok, let me know if you need anything else. Details

Cancel

Warning: Lengths of source and translation differ too much.
Ok, let me know if you need anything else.
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-03-01 05:46:40
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Expired caducado Details

Expired

Warning: The translation appears to be missing the initial uppercase.
caducado
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-03-01 05:46:49
Date added (local):
Calculating...
References:
Priority:
normal
More links:
  • Singular:
    %1$d record processed successfully, %2$d failed.
  • Plural:
    %1$d records processed successfully, %2$d failed.
  • Singular:
    %1$d registro procesado correctamente, %2$d falló.
  • Plural:
    %1$d registros procesados correctamente, %2$d fallaron.
Details

Singular:
%1$d record processed successfully, %2$d failed.

%1$d registro procesado correctamente, %2$d falló.
You have to log in to edit this translation.

Plural:
%1$d records processed successfully, %2$d failed.

%1$d registros procesados correctamente, %2$d fallaron.
You have to log in to edit this translation.

Meta

Status:
waiting
Comment:
translators: %1$d: number of records processed successfully, %2$d: number of records that failed
Date added (GMT):
2026-03-02 03:14:45
Date added (local):
Calculating...
References:
Priority:
normal
More links:
  • Singular:
    %d domain transfer has failed recently.
  • Plural:
    %d domain transfers have failed recently.
  • Singular:
    %d transferencia de dominio ha fallado recientemente.
  • Plural:
    %d transferencias de dominio han fallado recientemente.
Details

Singular:
%d domain transfer has failed recently.

%d transferencia de dominio ha fallado recientemente.
You have to log in to edit this translation.

Plural:
%d domain transfers have failed recently.

%d transferencias de dominio han fallado recientemente.
You have to log in to edit this translation.

Meta

Status:
waiting
Comment:
translators: %d: number of failed transfers
Date added (GMT):
2026-03-02 18:49:45
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Address dirección Details

Address

Warning: The translation appears to be missing the initial uppercase.
dirección
You have to log in to edit this translation.
Legend:
Current
Waiting
Rejected
Fuzzy
Old
With warnings
1

Export as