Les prix des forfaits de données GigSky varient en fonction de la devise qui est déterminée par les paramètres de région dans leur application.
Les prix des forfaits de données GigSky varient en fonction de la devise qui est déterminée par les paramètres de région dans leur application.
Les prix des forfaits de données GigSky varient en fonction de la devise qui est déterminée par les paramètres de région dans leur application.
Code Promo
GigSky ne propose pas de eSIM à données illimitées pour Lituanie. Les voyageurs qui souhaitent rester connectés à Lituanie peuvent choisir parmi les forfaits à données fixes de GigSky. Par exemple, un forfait de 100 GB valable 180 jours coûte 107,99 USD, tandis qu’un forfait de 50 GB valable 90 jours coûte 71,99 USD. Ces options à données fixes constituent une solution plus rentable pour les utilisateurs qui ont besoin d’un volume de données important sans nécessiter d’utilisation illimitée.
GigSky ne propose pas d’eSIM Lithuania incluant un numéro de téléphone local ou la capacité d’envoyer des SMS. Tous les plans GigSky pour Lithuania sont uniquement de données ; les voyageurs peuvent compter sur les applications VoIP courantes telles que WhatsApp, Telegram ou iMessage pour passer des appels et envoyer des messages via la connexion de données.
<|channel|>analysis<|message|>We need to translate the given English text into French, following instructions:
No extra text besides the translation.
No titles for translation.
Should not translate MNO, MVNO, etc. (not present).
Should not translate the names (masculin) of the providers: "GigSky". "GigSky" is a provider name; it stays as GigSky in French.
IMPORTANT: The following names are the names of eSIM plans and MUST NOT BE TRANSLATED WHEN THEY APPEAR AS PLAN NAME: "Lithuania"
Wait, the instruction says: "IMPORTANT: Les noms suivants sont des noms de forfaits/plans eSIM et NE DOIVENT PAS être traduits quand ils apparaissent comme nom de plan: "Lithuania""
But "Lithuania" is a name (country name). It's specified as a name of a plan? That's weird. But I think they imply that if the text refers to a plan named "Lithuania", we shouldn't translate that name.
But the text being translated says: "GigSky currently offers 14 single coverage data plans specifically for Lithuania, along with 30 multi-country plans that include Lithuania as part of their coverage." So there's no plan name "Lithuania"; it's referring to the country. So we can translate normally: "Lithuanie" in French. Wait, but the instruction says that "Lithuania" is a name of a plan and shouldn't be translated when it appears as a plan name. But we are not translating it as a plan name. It's a country name. The examples show: "Le plan Europe" remains "Le plan Europe" (not translated because it's a plan name). But if it's describing going to Europe, it's "Voyagez en Europe" which is translated normally.
Given "Lithuania" is a name of a plan, but in the text it's referring to coverage for that country, not the plan. The instruction says to not translate "Lithuania" when it's a plan name. But we don't see "Lithuania" as a plan name. Instead it's a country. Should we translate it?
The rule about "foreign words not to be translated" is for plan names. "Lithuania" is presumably a given plan title. But perhaps the text is about eSIM plans for Lithuania. "Lithuania" could be a plan name. But the text says "14 single coverage data plans specifically for Lithuania". That could be referring to 14 plans that each cover Lithuania exclusively. The word "Lithuania" appears as a country.
The instruction states avoid translating "Lithuania" if it appears as a plan name. But we need to determine if "Lithuania" appears as a plan name. Maybe the structure of the company: We have separate plan names like "Lithuania" as a plan name for coverage of Lithuania. So maybe it's like: the company sells a plan called "Lithuania". So "Lithuania" is a plan name. But the text uses it as a descriptor for coverage. It's ambiguous.
However, given the instructions, we should consider that if "Lithuania" refers to a plan, we don't translate. If it's a country, we translate normally. But I think the intention is to treat "Lithuania" as a plan name that is not to be translated. But we cannot modify the translation to something else. Let's check the instruction: "IMPORTANT: Les noms suivants sont des noms de forfaits/plans eSIM et NE DOIVENT PAS être traduits quand ils apparaissent comme nom de plan: "Lithuania". EXCEPTION: Si ces mots (comme "Europe", "France", etc.) sont utilisés dans le contexte général du texte et NON comme nom de forfait, ils DOIVENT être traduits normalement."
Thus it instructs: "Lithuania" is a name of a plan. But if "Lithuania" is used generally, we translate normally. So determine the context: The phrase says "14 single coverage data plans specifically for Lithuania". That refers to the country coverage. So it's general. So we can translate it as "Lithuanie" in French. But "Lithuania" isn't "Europe" or "France" but a country name; so the rule says if the word is used in general context, translate. So "Lithuania" -> "Lithuanie" in French. That is consistent.
Except the instruction says "NE DOIVENT PAS être traduits quand ils apparaissent comme nom de plan: "Lithuania"". But we announce we are not going to translate because it's a plan name? But authority says if plan names "Lithuania" appear, don't translate. But here it's used as the phrase "Lithuania" meaning coverage. I think but we might avoid confusion by leaving it as "Lithuania" in the translation. But if we translate "Lithuania" to "Lithuanie", could that create confusion? Let's read the instruction carefully: "IMPORTANT: Les noms suivants sont des noms de forfaits/plans eSIM et NE DOIVENT PAS être traduits quand ils apparaissent comme nom de plan: "Lithuania". EXCEPTION: Si ces mots (comme "Europe", "France", etc.) sont utilisés dans le contexte général du texte et NON comme nom de forfait, ils DOIVENT être traduits normalement."
Thus the plan names must not be translated. "Lithuania" is a plan name not to be translated when it's a plan name. Now, "Europe" is a generic term for a region and "France" is a country. They must be translated when used in normal context. But considers "The plan Europe" remains "Le plan Europe" (not translated). So for that, "Europe" is a plan name; so in "Le plan Europe" you don't translate "Europe".
But here we have "plans specifically for Lithuania" i.e. "plans for Lithuania" meaning "plans for coverage of Lithuania". But the name of the plan could be "Lithuania" as well. The context cannot be easily distinguished. The safe approach is to treat it as a plan name? But then we can't translate "Lithuania". But the instruction says "NE DOIVENT PAS être traduits quand ils apparaissent comme nom de plan." That means if the fragment "Lithuania" appears as a name of the plan. In our case, it's not "Le plan Lithuania"; it's "plans for Lithuania". So maybe it's not the name of the plan, just the country. So we could translate "Lithuania" to "Lithuanie".
Let's analyze the original English:
"GigSky currently offers 14 single coverage data plans specifically for Lithuania, along with 30 multi-country plans that include Lithuania as part of their coverage."
This means: "Il y a 14 forfaits de données couvrant une seule zone (Lithuania)."
So you could interpret "plans for Lithuania" as the plans cover only that country. We can translate "Lithuania" as "Lithuanie". That seems correct.
However, the instruction says if "Lithuania" appears as a plan name, do not translate. But there is no evidence that "Lithuania" is the plan name here. The phrase "plans specifically for Lithuania" implies the country context. So translation will use French word for "Lithuania" -> "Lithuanie".
Then we need to translate the rest: "GigSky currently offers 14 single coverage data plans specifically for Lithuania, along with 30 multi-country plans that include Lithuania as part of their coverage. These plans vary, with some offering a fixed data allowance ranging from 500MB to 100GB, and others providing a daily data cap. Prices for these plans range from $0.00 to $329.99, with validity periods spanning from 1 to 180 days."
We need to maintain the formatting: sentence structure, same numbers, units. Use "MB" is fine for "MB", "GB" as "GB", but we might keep measurement units same.
But we need to not translate "GigSky". The text used "GigSky" well.
Also to not translate "MNO", "MVNO" etc. Not present.
Also "the prices range from $0.00 to $329.99" we might keep as "$0.00 to $329.99" but maybe we need to translate to French format with €? But the instruction doesn't specify such conversion. Keep the same. We might just keep them as is: "$0.00 to $329.99".
But perhaps the question is about translating text into French, but keep prices as same format including dollars. That's fine.
Also the numeric values: "14", "30", "500MB", "100GB", "1 to 180" days, etc. Need to decide formatting: In French numeric formatting, we might use commas for decimal points? But that's not specified. The instruction doesn't say to adapt numeric formatting. So maybe we keep numeric values as in original.
Use "jours" for days.
We need to embed "GB" and "MB" as is? Usually in French, "GB" remains "Go" for gigabytes but that is a changes. The instruction says nothing about unit conversions. We might keep as "GB" or maybe convert "500MB" into "500 Mo" and "100GB" into "100 Go". But that might be considered translation but not required. They didn't instruct to modify content. We should probably keep unit abbreviations in English? But in French it's usually "Mo" for MB (Mégabyte) or "Go" for GB. But for eSIM plan context, maybe the provider uses same abbreviations. But the instruction didn't mention. We'll assume we preserve them but ensure proper spacing: "500 MB" and "100 GB" with thin space. But I'll maintain just "500 MB" and "100 GB". Or maybe keep "500 Mo" and "100 Go". But unsaid.
Better to keep consistent with original: "MB" and "GB". But is it acceptable in French? Possibly.
Also we might keep "$" and "0.00" number formatting, but the constraint: we don't add other text. Only translation, no titles.
Thus we shall produce exactly:
"GigSky currently offers 14 single coverage data plans specifically for Lithuania, along with 30 multi-country plans that include Lithuania as part of their coverage. These plans vary, with some offering a fixed data allowance ranging from 500MB to 100GB, and others providing a daily data cap. Prices for these plans range from $0.00 to $329.99, with validity periods spanning from 1 to 180 days."
In French:
"GigSky propose actuellement 14 forfaits de données à couverture unique spécifiquement pour la Lituanie, ainsi que 30 forfaits multi-pays incluant la Lituanie dans leur zone de couverture. Ces forfaits varient : certains offrent une allocation de données fixe allant de 500 MB à 100 GB, d’autres proposent une limite quotidienne de données. Les prix de ces forfaits vont de 0,00 $ à 329,99 $, avec des périodes de validité allant de 1 à 180 jours."
But we have to think carefully about the translation.
Let's manage grammar.
"GigSky currently offers" → "GigSky propose actuellement"
"14 single coverage data plans specifically for Lithuania" → "14 forfaits de données à couverture unique spécifiquement pour la Lituanie"
We need to keep the phrase "single coverage" as "à couverture unique" or "monopays" but "single coverage" means "unique coverage" but it's ambiguous. Might be "à couverture unique". French use "forfaits de données à couverture unique". That's fine.
Alternatively: "ainsi que 30 forfaits à couverture multi-pays incluant la Lituanie dans leur zone de couverture." That may be better.
"These plans vary" → "Ces forfaits varient"
"with some offering a fixed data allowance ranging from 500MB to 100GB" → "certains offrant une allocation de données fixe allant de 500 MB à 100 GB"
"and others providing a daily data cap." → "et d’autres s’établissant sur un plafond quotidien." But "daily data cap" could be "limite quotidienne de données". That might be more accurate. "supplément**"? "offre une limite quotidienne de données" would be "with other allowing a daily data cap".
We can say: "et d'autres proposant un plafond quotidien de données." Or "et d'autres offrant une limite quotidienne de données". This is okay.
But the original had a dollar sign; maybe preserve the dollar sign. French currency may use "$" or "USD", but it's fine.
We should keep numeric formatting consistent: The last phrase indicates days.
In French, numeric ranges would be "de 1 à 180 jours." We represent 1 days as "1" but we keep decimal? We need to decide if "1 to 180" should be "1 à 180" days. That is fine.
Make sure we use a space on the left side of currency symbol? In French, typical usage: "0,00 $" no space? There is an international usage: "0,00 $" with a non-breaking space before the symbol. In English, we wrote "$0.00". In French, we could use "$0,00". But keep as "$0.00"? The instruction doesn't require altering currency formatting. But we might keep "$0.00" because we are transliterating. However, the requirement: "Translate the text in French." This likely expects proper formatting in French. But sometimes not necessary. The instruction didn't mention currency conversions, but might want to preserve original format for clarity. It's ambiguous.
But we could keep the dollar sign as is: "$0.00". It's fine.
But in French, $0.00 and $329.99 might not be typical. Usually, we would not use the "$" sign or use "USD". But return of translation often preserve original formatting. The instruction doesn't require converting currency. So keep the original "$0.00" as is, but ensure colon usage with decimal.
However, maybe the best approach: "de 0,00 $ à 329,99 $" but keep decimal points as period? The original uses decimal period while French uses decimal comma. But the instructions said translation only. It didn't mention to convert numeric comma decimal. So, might not change.
But also we're told: "N'ajoute pas d'autre texte que la traduction." So we cannot provide explanation. So just translation.
Thus the translation:
"GigSky propose actuellement 14 forfaits de données à couverture unique spécifiquement pour la Lituanie, ainsi que 30 forfaits multi-pays qui incluent la Lituanie dans leur zone de couverture. Ces forfaits varient, certains offrant une allocation de données fixe allant de 500 MB à 100 GB, d’autres proposant un plafond quotidien de données. Les prix de ces forfaits vont de 0,00 $ à 329,99 $, avec des périodes de validité allant de 1 à 180 jours."
We need to check if we didn't inadvertently translate "Lithuania" as a plan name. We kept "la Lituanie" as a country. That's okay.
We also need to keep "GigSky" unchanged.
We need to check whether "multi-country" used "multi-pays" or "multi-pays"? Typical translation is "multi-pays". Yes.
Alternate phrasing: "forfaits à couverture multi-pays" is more natural. But that might add "à" again. Could be "forfaits multi-pays". That is okay.
Also "single coverage" translation "à couverture unique" or "pour un pays only"? "single coverage" might refer to "covering only one country". But we can keep "à couverture unique". That's okay.
But we might consider "forfaits de données monopays" but that's too technical. Keep "forfaits à couverture unique".
Also "data plans" -> "forfaits de données". It's fine.
Now, check the instructions: "Ne pas traduire MNO, MVNO, etc." They are not present.
Check for "GigSky" we keep it the same.
Also check "Lithuania" we kept "la Lituanie". The instruction: "NE DOIVENT PAS être traduits quand ils apparaissent comme nom de plan: 'Lithuania'". But it's not a name of a plan. So translation is okay.
The exception: "Si ces mots (like 'Europe', 'France', etc.) are used in the general context ... they DO MUST be translated normally." So we must translate "Lithuania" to French. Yes.
Thus correct.
But we may need to adjust punctuation: original text: "GigSky currently offers 14 ... days." Each sentence ended with period. We'll keep the correct French punctuation: period. Keep the same overall structure of 4 sentences.
Now check any other translation choices:
"range from" -> "allant de ... à ..." or "varient de ... à ...". Use "varient de ... à ..." for price. Fine.
"validity periods spanning from 1 to 180 days." -> "périodes de validité allant de 1 à 180 jours." Good.
The "data allowances" -> "allocation de données fixe".
"daily data cap" -> "plafond quotidien de données" or "limite quotidienne de données".
We can use "plafond quotidien de données" but not "plafond quotidien". Should be fine.
Let's produce translation:
"GigSky propose actuellement 14 forfaits de données à couverture unique spécifiquement pour la Lituanie, ainsi que 30 forfaits multi-pays qui incluent la Lituanie dans leur zone de couverture. Ces forfaits varient, certains offrant une allocation de données fixe allant de 500 MB à 100 GB, d’autres proposant un plafond quotidien de données. Les prix de ces forfaits vont de $0.00 à $329.99, avec des périodes de validité allant de 1 à 180 jours."
We need to decide on formatting: 500 MB and 100 GB include a non-breaking space? We can use normal space. But we'll add narrow non-breaking should be fine.
Also "0.00" should not convert comma.
But in French we might use decimals as "0,00"? But unchanged? But instruction: "Do not translate MNO, MVNO, etc." No mention about decimal separators. So we might keep them as "0.00". Might cause inconsistencies but it's not disallowed. The French also might use decimal comma, but it's not required.
Given we are translating, likely to keep the same formatting for numeric values. So 0.00 and 329.99 remain with dot. We'll keep same.
Thus final translation:
"GigSky propose actuellement 14 forfaits de données à couverture unique spécifiquement pour la Lituanie, ainsi que 30 forfaits multi-pays qui incluent la Lituanie dans leur zone de couverture. Ces forfaits varient, certains offrant une allocation de données fixe allant de 500 MB à 100 GB, d’autres proposant un plafond quotidien de données. Les prix de ces forfaits vont de $0.00 à $329.99, avec des périodes de validité allant de 1 à 180 jours."
Double-check all words: "propose" vs "offers" is good. "actuellement" corresponds to "currently". All good.
But we might want to preserve bullet bullet? "14 single coverage data plans specifically for Lithuania" -> "14 forfaits de données à couverture unique spécifiquement pour la Lituanie" is correct.
We might add "de" before "14" but it's not necessary? But "14 forfaits" is correct.
The plural of "forfait" is "forfaits". That's correct.
Now let's examine the instruction: "NE PAS Traduire MNO, MVNO, etc." None present.
Also: "Ne pas traduire les noms" "GigSky" stays as is.
We also need to keep "Lithuania" as a plan name if it's used as a plan name. But we used "la Lituanie". That's a translation.
We need to verify if "Lithuania" is used as a plan name. In the text: "the 30 multi-country plans that include Lithuania as part of their coverage." It's a reference to the country. So translation should be "la Lituanie" accordingly. That is consistent.
We must not add a title or extra text. So just the translation.
But let's consider if something else needs to be considered: The original text uses "14 single coverage data plans specifically for Lithuania," i.e., 14 plans that cover single country only. In French, we could say "14 forfaits de données à couverture unique" or "14 forfaits à couverture unique". Good.
Second part: "30 multi-country plans that include Lithuania as part of their coverage" -> "30 forfaits multi-pays qui incluent la Lituanie dans leur zone de couverture." or "30 forfaits à couverture multi-pays qui incluent la Lituanie". Both are fine. We'll maintain.
Third: "These plans vary, with some offering a fixed data allowance ranging from 500MB to 100GB, and others providing a daily data cap." -> "Ces forfaits varient, certains offrant une allocation de données fixe allant de 500 MB à 100 GB, d’autres proposant un plafond quotidien de données." Good.
Fourth: "Prices for these plans range from $0.00 to $329.99, with validity periods spanning from 1 to 180 days." -> "Les prix de ces forfaits varient de $0.00 à $329.99, avec des périodes de validité allant de 1 à 180 jours." We might use "varient de" instead of "vont de". Use "varient" for price variation. It's a possibility. The sentence originally: "Prices ... range from ...". So we can keep "varient de". That is better.
Thus final translation:
"GigSky propose actuellement 14 forfaits de données à couverture unique spécifiquement pour la Lituanie, ainsi que 30 forfaits multi-pays qui incluent la Lituanie dans leur zone de couverture. Ces forfaits varient, certains offrant une allocation de données fixe allant de 500 MB à 100 GB, d’autres proposant un plafond quotidien de données. Les prix de ces forfaits varient de $0.00 à $329.99, avec des périodes de validité allant de 1 à 180 jours."
But maybe we want "La Lituanie" as "la Lituanie"? The French name for Lithuania is "Lituanie". So we say "la Lituanie". Yes.
But maybe we want "en Lituanie" instead of "pour la Lituanie"? "for the Lituanie" is "for Lituanie". But "spécifiquement pour la Lituanie" is correct.
Thus we have translation.
Let's check for polishini: the phrase "14 forfaits de données à couverture unique spécifiquement pour la Lituanie, ainsi que 30 forfaits multi-pays qui incluent la Lituanie dans leur zone de couverture." The mention "spécifiquement pour la Lituanie" might be redundant after "for de données à couverture unique". Might be "spécifiquement pour la Lituanie" is ok. But we might also write "spécifiquement pour la Lituanie" or "spécifiquement destinés à la Lituanie". But keep as is.
Now we need to ensure we didn't inadvertently translate "Lithuania" as a plan. In French we used "la Lituanie". It's a translation for the country. But we might also keep the "Lithuania" as "Lithuania" to avoid mismatch with instruction. But do we need to? The instruction says not to translate "Lithuania" when it appears as a plan name. But regarding usage as a general context, we should translate. So yes, we should translate.
Thus our translation is correct.
But let's read the instruction again: "NE DOIVENT PAS être traduits quand ils apparaissent comme nom de plan: "Lithuania". EXCEPTION: Si ces mots (comme "Europe", "France", etc.) sont utilisés dans le contexte général du texte et NON comme nom de forfait, ils DOIVENT être traduits normalement."
Thus "Lithuania" would be considered a plan name when used as a title or name of a plan. But here is not a plan name. So we translate. Good.
Now we must not add a title. So only translation.
Let's double-check each word:
"GigSky propose actuellement" correct.
"14 forfaits de données à couverture unique spécifiquement pour la Lituanie" correct.
At the same time, "spécifiquement pour la Lituanie" maybe double context. But okay.
"ainsi que 30 forfaits multi-pays qui incluent la Lituanie dans leur zone de couverture." Good.
"Ces forfaits varient, certains offrant une allocation de données fixe allant de 500 MB à 100 GB, d’autres proposant un plafond quotidien de données." That is a single sentence with a comma after varient, maybe "Ces forfaits varient ; certains offrant ... d’autres proposant ...". But they used a comma and a semicolon. But we kept a comma. Good.
"Les prix de ces forfaits varient de $0.00 à $329.99, avec des périodes de validité allant de 1 à 180 jours." Good.
Check if we used "varient" or "vont". We used "varient".
Now check for extra spaces: We integrated non-breaking spaces between number and unit: 500 MB, 100 GB. Should we use narrow non-breaking space? In text we can just use standard space. Not necessary.
Better to use "500 MB" with narrow non-breaking spaces but they don't ask to. So use "500 MB", "100 GB". But let's be consistent.
Better to keep "500 MB" "100 GB". But earlier we wrote "500 MB" with narrow space. It's fine.
We'll write "500 MB" with a normal space. But either is fine.
But maybe we should keep "500 MB" two characters. But answer can be plain.
Now also keep punctuation: use apostrophes for andere "d’autres" with accent. Good.
We'll produce final answer:
"GigSky propose actuellement 14 forfaits de données à couverture unique spécifiquement pour la Lituanie, ainsi que 30 forfaits multi-pays qui incluent la Lituanie dans leur zone de couverture. Ces forfaits varient, certains offrant une allocation de données fixe allant de 500 MB à 100 GB, d’autres proposant un plafond quotidien de données. Les prix de ces forfaits varient de $0.00 à $329.99, avec des périodes de validité allant de 1 à 180 jours."
Yes. should be fine.
But ensure we don't include trailing spaces or period after last sentence. The last sentence ends with a period. Good.
Let's produce.
I will produce the translation exactly.<|end|><|start|>assistant<|channel|>final<|message|>GigSky propose actuellement 14 forfaits de données à couverture unique spécifiquement pour la Lituanie, ainsi que 30 forfaits multi-pays qui incluent la Lituanie dans leur zone de couverture. Ces forfaits varient, certains offrant une allocation de données fixe allant de 500 MB à 100 GB, d’autres proposant un plafond quotidien de données. Les prix de ces forfaits varient de $0.00 à $329.99, avec des périodes de validité allant de 1 à 180 jours.
Résumé avec Gen AI. Dernière mise à jour: