From 9898fb3fb9dddc68c0173da8069cdf21723aaa27 Mon Sep 17 00:00:00 2001 From: enessmr <136172887+enessmr@users.noreply.github.com> Date: Sat, 8 Mar 2025 23:08:58 +0300 Subject: [PATCH 1/6] Update system.js TRANSLATION... WOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO --- .config/ags/modules/bar/normal/system.js | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.config/ags/modules/bar/normal/system.js b/.config/ags/modules/bar/normal/system.js index 41f3eff68..0aef4bf56 100644 --- a/.config/ags/modules/bar/normal/system.js +++ b/.config/ags/modules/bar/normal/system.js @@ -169,12 +169,13 @@ const BatteryModule = () => Stack({ .catch(print); const weatherCode = weather.current_condition[0].weatherCode; const weatherDesc = weather.current_condition[0].weatherDesc[0].value; + const translatedWeatherDesc = getString(weatherDesc) || weatherDesc; const temperature = weather.current_condition[0][`temp_${userOptions.weather.preferredUnit}`]; const feelsLike = weather.current_condition[0][`FeelsLike${userOptions.weather.preferredUnit}`]; const weatherSymbol = WEATHER_SYMBOL[WWO_CODE[weatherCode]]; self.children[0].label = weatherSymbol; self.children[1].label = `${temperature}°${userOptions.weather.preferredUnit} • ${getString('Feels like')} ${feelsLike}°${userOptions.weather.preferredUnit}`; - self.tooltipText = weatherDesc; + self.tooltipText = translatedWeatherDesc; }).catch((err) => { try { // Read from cache const weather = JSON.parse( From 9d4b68261d8d784d926820d5862764cde167f2b8 Mon Sep 17 00:00:00 2001 From: enessmr <136172887+enessmr@users.noreply.github.com> Date: Sat, 8 Mar 2025 23:11:26 +0300 Subject: [PATCH 2/6] Update fa_IR.json --- .config/ags/i18n/locales/fa_IR.json | 33 ++++++++++++++++++++++++++++- 1 file changed, 32 insertions(+), 1 deletion(-) diff --git a/.config/ags/i18n/locales/fa_IR.json b/.config/ags/i18n/locales/fa_IR.json index c0837de0f..6770305fa 100644 --- a/.config/ags/i18n/locales/fa_IR.json +++ b/.config/ags/i18n/locales/fa_IR.json @@ -237,5 +237,36 @@ "Save image": "نگه‌داری تصویر", "Hoard": "نگه‌داری", "Open externally": "باز کردن در", - "You are an assistant on a sidebar of a Wayland Linux desktop. Please always use a casual tone when answering your questions, unless requested otherwise or making writing suggestions. These are the steps you should take to respond to the user's queries:\n1. If it's a writing- or grammar-related question or a sentence in quotation marks, Please point out errors and correct when necessary using underlines, and make the writing more natural where appropriate without making too major changes. If you're given a sentence in quotes but is grammatically correct, explain briefly concepts that are uncommon.\n2. If it's a question about system tasks, give a bash command in a code block with brief explanation.\n3. Otherwise, when asked to summarize information or explaining concepts, you are should use bullet points and headings. For mathematics expressions, you *have to* use LaTeX within a code block with the language set as \"latex\". \nNote: Use casual language, be short, while ensuring the factual correctness of your response. If you are unsure or don’t have enough information to provide a confident answer, simply say “I don’t know” or “I’m not sure.”. \nThanks!": "You are an assistant on a sidebar of a Wayland Linux desktop. Please always use a casual tone when answering your questions, unless requested otherwise or making writing suggestions. These are the steps you should take to respond to the user's queries:\n1. If it's a writing- or grammar-related question or a sentence in quotation marks, Please point out errors and correct when necessary using underlines, and make the writing more natural where appropriate without making too major changes. If you're given a sentence in quotes but is grammatically correct, explain briefly concepts that are uncommon.\n2. If it's a question about system tasks, give a bash command in a code block with brief explanation.\n3. Otherwise, when asked to summarize information or explaining concepts, you are should use bullet points and headings. For mathematics expressions, you *have to* use LaTeX within a code block with the language set as \"latex\". \nNote: Use casual language, be short, while ensuring the factual correctness of your response. If you are unsure or don’t have enough information to provide a confident answer, simply say “I don’t know” or “I’m not sure.”. \nIf user talks to you in Persian and you can also respond in Persian, definitely respond in Persian. Thanks!" + "You are an assistant on a sidebar of a Wayland Linux desktop. Please always use a casual tone when answering your questions, unless requested otherwise or making writing suggestions. These are the steps you should take to respond to the user's queries:\n1. If it's a writing- or grammar-related question or a sentence in quotation marks, Please point out errors and correct when necessary using underlines, and make the writing more natural where appropriate without making too major changes. If you're given a sentence in quotes but is grammatically correct, explain briefly concepts that are uncommon.\n2. If it's a question about system tasks, give a bash command in a code block with brief explanation.\n3. Otherwise, when asked to summarize information or explaining concepts, you are should use bullet points and headings. For mathematics expressions, you *have to* use LaTeX within a code block with the language set as \"latex\". \nNote: Use casual language, be short, while ensuring the factual correctness of your response. If you are unsure or don’t have enough information to provide a confident answer, simply say “I don’t know” or “I’m not sure.”. \nThanks!": "You are an assistant on a sidebar of a Wayland Linux desktop. Please always use a casual tone when answering your questions, unless requested otherwise or making writing suggestions. These are the steps you should take to respond to the user's queries:\n1. If it's a writing- or grammar-related question or a sentence in quotation marks, Please point out errors and correct when necessary using underlines, and make the writing more natural where appropriate without making too major changes. If you're given a sentence in quotes but is grammatically correct, explain briefly concepts that are uncommon.\n2. If it's a question about system tasks, give a bash command in a code block with brief explanation.\n3. Otherwise, when asked to summarize information or explaining concepts, you are should use bullet points and headings. For mathematics expressions, you *have to* use LaTeX within a code block with the language set as \"latex\". \nNote: Use casual language, be short, while ensuring the factual correctness of your response. If you are unsure or don’t have enough information to provide a confident answer, simply say “I don’t know” or “I’m not sure.”. \nIf user talks to you in Persian and you can also respond in Persian, definitely respond in Persian. Thanks!", + "Sunny": "آفتابی", + "PartlyCloudy": "نیمه ابری", + "Cloudy": "ابری", + "VeryCloudy": "بسیار ابری", + "Fog": "مه آلود", + "LightShowers": "باران سبک", + "LightSleetShowers": "باران و برف سبک", + "LightSleet": "برف و باران سبک", + "ThunderyShowers": "رگبار همراه با رعد و برق", + "LightSnow": "برف سبک", + "HeavySnow": "برف سنگین", + "LightRain": "باران سبک", + "HeavyShowers": "رگبار شدید", + "HeavyRain": "باران شدید", + "LightSnowShowers": "رگبار برف سبک", + "HeavySnowShowers": "رگبار برف سنگین", + "ThunderyHeavyRain": "باران شدید همراه با رعد و برق", + "Partly Cloudy": "نیمه ابری", + "Very Cloudy": "بسیار ابری", + "Light Showers": "باران سبک", + "Light Sleet Showers": "باران و برف سبک", + "Light Sleet": "برف و باران سبک", + "Thundery Showers": "رگبار همراه با رعد و برق", + "Light Snow": "برف سبک", + "Heavy Snow": "برف سنگین", + "Light Rain": "باران سبک", + "Heavy Showers": "رگبار شدید", + "Heavy Rain": "باران شدید", + "Light Snow Showers": "رگبار برف سبک", + "Heavy Snow Showers": "رگبار برف سنگین", + "Thundery Heavy Rain": "باران شدید همراه با رعد و برق" } From ae16287384d831d75ddfeecef9bc8dbc0f163376 Mon Sep 17 00:00:00 2001 From: enessmr <136172887+enessmr@users.noreply.github.com> Date: Sat, 8 Mar 2025 23:12:59 +0300 Subject: [PATCH 3/6] Update fr_FR.json --- .config/ags/i18n/locales/fr_FR.json | 35 +++++++++++++++++++++++++++-- 1 file changed, 33 insertions(+), 2 deletions(-) diff --git a/.config/ags/i18n/locales/fr_FR.json b/.config/ags/i18n/locales/fr_FR.json index d21789164..45f70393d 100644 --- a/.config/ags/i18n/locales/fr_FR.json +++ b/.config/ags/i18n/locales/fr_FR.json @@ -238,6 +238,37 @@ "Hoard": "Accumuler", "Open externally": "Ouvrir avec une application externe", "You are an assistant on a sidebar of a Wayland Linux desktop. Please always use a casual tone when answering your questions, unless requested otherwise or making writing suggestions. These are the steps you should take to respond to the user's queries:\n1. If it's a writing- or grammar-related question or a sentence in quotation marks, Please point out errors and correct when necessary using underlines, and make the writing more natural where appropriate without making too major changes. If you're given a sentence in quotes but is grammatically correct, explain briefly concepts that are uncommon.\n2. If it's a question about system tasks, give a bash command in a code block with brief explanation.\n3. Otherwise, when asked to summarize information or explaining concepts, you are should use bullet points and headings. For mathematics expressions, you *have to* use LaTeX within a code block with the language set as \"latex\". \nNote: Use casual language, be short, while ensuring the factual correctness of your response. If you are unsure or don’t have enough information to provide a confident answer, simply say “I don’t know” or “I'm not sure.”. \nThanks!": "Tu es un assistant dans un panneau latéral d'un bureau Linux sous Wayland. Veilles à toujours adopter un ton décontracté lorsque tu réponds, sauf indication contraire ou lors de suggestions d'écriture. Voici les étapes à suivre pour répondre aux requêtes de l'utilisateur :\n1. S'il s'agit d'une question liée à l'écriture ou à la grammaire, ou d'une phrase entre guillemets, signales les erreurs et corriges-les si nécessaire en utilisant des soulignements, et rends l'écriture plus naturelle lorsque cela est approprié sans apporter de modifications trop importantes. Si on te fournit une phrase entre guillemets mais grammaticalement correcte, expliques brièvement des concepts peu communs.\n2. S'il s'agit d'une question concernant des tâches système, fournis une commande bash dans un bloc de code avec une brève explication.\n3. Sinon, lorsqu'on te demande de résumer des informations ou d'expliquer des concepts, utilises des puces et des titres. Pour les expressions mathématiques, tu *dois* utiliser LaTeX dans un bloc de code avec la langue définie sur \"latex\".\nNote : Utilises un langage décontracté, sois bref, tout en garantissant l'exactitude des informations de ta réponse. Si tu n'es pas sûr ou si tu ne disposes pas d'assez d'informations pour fournir une réponse convaincante, dis simplement \"Je ne sais pas\" ou \"Je ne suis pas sûr\".\nMerci !", - "Feels like": "Ressenti" + "Feels like": "Ressenti", + "Sunny": "Ensoleillé", + "PartlyCloudy": "Partiellement nuageux", + "Cloudy": "Nuageux", + "VeryCloudy": "Très nuageux", + "Fog": "Brouillard", + "LightShowers": "Averses légères", + "LightSleetShowers": "Averses de neige fondue légères", + "LightSleet": "Neige fondue légère", + "ThunderyShowers": "Averses orageuses", + "LightSnow": "Neige légère", + "HeavySnow": "Neige abondante", + "LightRain": "Pluie légère", + "HeavyShowers": "Forte averse", + "HeavyRain": "Pluie forte", + "LightSnowShowers": "Averses de neige légère", + "HeavySnowShowers": "Averses de neige abondante", + "ThunderyHeavyRain": "Pluie forte avec orages", + "Partly Cloudy": "Partiellement nuageux", + "Very Cloudy": "Très nuageux", + "Light Showers": "Averses légères", + "Light Sleet Showers": "Averses de neige fondue légères", + "Light Sleet": "Neige fondue légère", + "Thundery Showers": "Averses orageuses", + "Light Snow": "Neige légère", + "Heavy Snow": "Neige abondante", + "Light Rain": "Pluie légère", + "Heavy Showers": "Forte averse", + "Heavy Rain": "Pluie forte", + "Light Snow Showers": "Averses de neige légère", + "Heavy Snow Showers": "Averses de neige abondante", + "Thundery Heavy Rain": "Pluie forte avec orages" } - \ No newline at end of file + From 8f99faa0cf36c7ac94a845ef6d5cb382fec83c30 Mon Sep 17 00:00:00 2001 From: enessmr <136172887+enessmr@users.noreply.github.com> Date: Sat, 8 Mar 2025 23:15:12 +0300 Subject: [PATCH 4/6] Update it_IT.json --- .config/ags/i18n/locales/it_IT.json | 36 +++++++++++++++++++++++++++-- 1 file changed, 34 insertions(+), 2 deletions(-) diff --git a/.config/ags/i18n/locales/it_IT.json b/.config/ags/i18n/locales/it_IT.json index f2fdc6d1c..0029fa467 100644 --- a/.config/ags/i18n/locales/it_IT.json +++ b/.config/ags/i18n/locales/it_IT.json @@ -237,5 +237,37 @@ "Save image": "Salva immagine", "Hoard": "Accumula", "Open externally": "Apri esternamente", - "You are an assistant on a sidebar of a Wayland Linux desktop. Please always use a casual tone when answering your questions, unless requested otherwise or making writing suggestions. These are the steps you should take to respond to the user's queries:\n1. If it's a writing- or grammar-related question or a sentence in quotation marks, Please point out errors and correct when necessary using underlines, and make the writing more natural where appropriate without making too major changes. If you're given a sentence in quotes but is grammatically correct, explain briefly concepts that are uncommon.\n2. If it's a question about system tasks, give a bash command in a code block with brief explanation.\n3. Otherwise, when asked to summarize information or explaining concepts, you are should use bullet points and headings. For mathematics expressions, you *have to* use LaTeX within a code block with the language set as \"latex\". \nNote: Use casual language, be short, while ensuring the factual correctness of your response. If you are unsure or don’t have enough information to provide a confident answer, simply say “I don’t know” or “I’m not sure.”. \nThanks!": "Sei un assistente nella barra laterale di un desktop Wayland Linux. Usa sempre un tono informale quando rispondi alle domande, a meno che non venga richiesto diversamente o quando fai suggerimenti di scrittura. Ecco i passaggi che devi seguire per rispondere alle domande dell'utente:\n1. Se si tratta di una domanda sulla scrittura o sulla grammatica o di una frase tra virgolette, segnala gli errori e correggi quando necessario utilizzando sottolineature, e rendi la scrittura più naturale dove appropriato senza fare modifiche troppo importanti. Se ti viene data una frase tra virgolette ma è grammaticalmente corretta, spiega brevemente concetti che sono poco comuni.\n2. Se è una domanda su attività di sistema, fornisci un comando bash in un blocco di codice con una breve spiegazione.\n3. Altrimenti, quando ti viene chiesto di riassumere informazioni o spiegare concetti, usa punti elenco e titoli. Per espressioni matematiche, *devi* usare LaTeX all'interno di un blocco di codice con il linguaggio impostato su \"latex\". \nNota: usa un linguaggio informale, sii breve, assicurandoti della correttezza fattuale della tua risposta. Se non sei sicuro o non hai abbastanza informazioni per fornire una risposta sicura, semplicemente dici “Non lo so” o “Non sono sicuro”. \nGrazie!" -} \ No newline at end of file + "You are an assistant on a sidebar of a Wayland Linux desktop. Please always use a casual tone when answering your questions, unless requested otherwise or making writing suggestions. These are the steps you should take to respond to the user's queries:\n1. If it's a writing- or grammar-related question or a sentence in quotation marks, Please point out errors and correct when necessary using underlines, and make the writing more natural where appropriate without making too major changes. If you're given a sentence in quotes but is grammatically correct, explain briefly concepts that are uncommon.\n2. If it's a question about system tasks, give a bash command in a code block with brief explanation.\n3. Otherwise, when asked to summarize information or explaining concepts, you are should use bullet points and headings. For mathematics expressions, you *have to* use LaTeX within a code block with the language set as \"latex\". \nNote: Use casual language, be short, while ensuring the factual correctness of your response. If you are unsure or don’t have enough information to provide a confident answer, simply say “I don’t know” or “I’m not sure.”. \nThanks!": "Sei un assistente nella barra laterale di un desktop Wayland Linux. Usa sempre un tono informale quando rispondi alle domande, a meno che non venga richiesto diversamente o quando fai suggerimenti di scrittura. Ecco i passaggi che devi seguire per rispondere alle domande dell'utente:\n1. Se si tratta di una domanda sulla scrittura o sulla grammatica o di una frase tra virgolette, segnala gli errori e correggi quando necessario utilizzando sottolineature, e rendi la scrittura più naturale dove appropriato senza fare modifiche troppo importanti. Se ti viene data una frase tra virgolette ma è grammaticalmente corretta, spiega brevemente concetti che sono poco comuni.\n2. Se è una domanda su attività di sistema, fornisci un comando bash in un blocco di codice con una breve spiegazione.\n3. Altrimenti, quando ti viene chiesto di riassumere informazioni o spiegare concetti, usa punti elenco e titoli. Per espressioni matematiche, *devi* usare LaTeX all'interno di un blocco di codice con il linguaggio impostato su \"latex\". \nNota: usa un linguaggio informale, sii breve, assicurandoti della correttezza fattuale della tua risposta. Se non sei sicuro o non hai abbastanza informazioni per fornire una risposta sicura, semplicemente dici “Non lo so” o “Non sono sicuro”. \nGrazie!", + "Feels like": "sembra come", + "Sunny": "Soleggiato", + "PartlyCloudy": "Parzialmente nuvoloso", + "Cloudy": "Nuvoloso", + "VeryCloudy": "Molto nuvoloso", + "Fog": "Nebbia", + "LightShowers": "Rovesci leggeri", + "LightSleetShowers": "Rovesci di nevischio leggeri", + "LightSleet": "Nevischio leggero", + "ThunderyShowers": "Rovesci temporaleschi", + "LightSnow": "Neve leggera", + "HeavySnow": "Neve forte", + "LightRain": "Pioggia leggera", + "HeavyShowers": "Rovesci forti", + "HeavyRain": "Pioggia forte", + "LightSnowShowers": "Rovesci di neve leggera", + "HeavySnowShowers": "Rovesci di neve forte", + "ThunderyHeavyRain": "Pioggia forte con temporali", + "Partly Cloudy": "Parzialmente nuvoloso", + "Very Cloudy": "Molto nuvoloso", + "Light Showers": "Rovesci leggeri", + "Light Sleet Showers": "Rovesci di nevischio leggeri", + "Light Sleet": "Nevischio leggero", + "Thundery Showers": "Rovesci temporaleschi", + "Light Snow": "Neve leggera", + "Heavy Snow": "Neve forte", + "Light Rain": "Pioggia leggera", + "Heavy Showers": "Rovesci forti", + "Heavy Rain": "Pioggia forte", + "Light Snow Showers": "Rovesci di neve leggera", + "Heavy Snow Showers": "Rovesci di neve forte", + "Thundery Heavy Rain": "Pioggia forte con temporali" +} From ce3976b0ba97d2a48b9f4e900f476c3614dbd209 Mon Sep 17 00:00:00 2001 From: enessmr <136172887+enessmr@users.noreply.github.com> Date: Sat, 8 Mar 2025 23:16:44 +0300 Subject: [PATCH 5/6] Update zh_CN.json --- .config/ags/i18n/locales/zh_CN.json | 33 ++++++++++++++++++++++++++++- 1 file changed, 32 insertions(+), 1 deletion(-) diff --git a/.config/ags/i18n/locales/zh_CN.json b/.config/ags/i18n/locales/zh_CN.json index c37fcb5b3..f4ee804cd 100644 --- a/.config/ags/i18n/locales/zh_CN.json +++ b/.config/ags/i18n/locales/zh_CN.json @@ -238,5 +238,36 @@ "Hoard": "保存", "Open externally": "在外部打开", "You are an assistant on a sidebar of a Wayland Linux desktop. Please always use a casual tone when answering your questions, unless requested otherwise or making writing suggestions. These are the steps you should take to respond to the user's queries:\n1. If it's a writing- or grammar-related question or a sentence in quotation marks, Please point out errors and correct when necessary using underlines, and make the writing more natural where appropriate without making too major changes. If you're given a sentence in quotes but is grammatically correct, explain briefly concepts that are uncommon.\n2. If it's a question about system tasks, give a bash command in a code block with brief explanation.\n3. Otherwise, when asked to summarize information or explaining concepts, you are should use bullet points and headings. For mathematics expressions, you *have to* use LaTeX within a code block with the language set as \"latex\". \nNote: Use casual language, be short, while ensuring the factual correctness of your response. If you are unsure or don’t have enough information to provide a confident answer, simply say “I don’t know” or “I’m not sure.”. \nThanks!": "你是 Wayland Linux 桌面侧边栏上的助手。除非有其他要求或提供建议，否则请始终保持轻松的语气回答问题。这是你回答用户查询的步骤：\n1. 如果是写作或语法相关的问题，或者引号中的句子，请指出错误并在必要时进行更正，使用下划线，并在适当的地方使写作更自然，不要进行太大更改。如果你给出的句子在引号中但语法正确，请简要解释不常见概念。\n2. 如果是关于系统任务的问题，请给出bash命令，并在代码块中简要说明。\n3. 否则，在总结信息或解释概念时，你应该使用项目符号和标题。对于数学表达式，你必须在代码块中使用 LaTeX，并将语言设置为\"latex\"。\n注意：使用轻松的语言，简洁，同时确保回答的事实正确性。如果你不确定或没有足够的信息来提供自信的答案，只需说“我不知道”或“我不确定”。\n谢谢！", - "Feels like": "体感温度" + "Feels like": "体感温度", + "Sunny": "晴朗", + "PartlyCloudy": "局部多云", + "Cloudy": "多云", + "VeryCloudy": "阴天", + "Fog": "雾", + "LightShowers": "小阵雨", + "LightSleetShowers": "小雨夹雪", + "LightSleet": "小雨雪", + "ThunderyShowers": "雷阵雨", + "LightSnow": "小雪", + "HeavySnow": "大雪", + "LightRain": "小雨", + "HeavyShowers": "大阵雨", + "HeavyRain": "大雨", + "LightSnowShowers": "小雪阵", + "HeavySnowShowers": "大雪阵", + "ThunderyHeavyRain": "雷暴大雨", + "Partly Cloudy": "局部多云", + "Very Cloudy": "阴天", + "Light Showers": "小阵雨", + "Light Sleet Showers": "小雨夹雪", + "Light Sleet": "小雨雪", + "Thundery Showers": "雷阵雨", + "Light Snow": "小雪", + "Heavy Snow": "大雪", + "Light Rain": "小雨", + "Heavy Showers": "大阵雨", + "Heavy Rain": "大雨", + "Light Snow Showers": "小雪阵", + "Heavy Snow Showers": "大雪阵", + "Thundery Heavy Rain": "雷暴大雨" } From 5cdcf60695a685f4eeb6d93c660391a9f7ff26be Mon Sep 17 00:00:00 2001 From: enessmr <136172887+enessmr@users.noreply.github.com> Date: Sat, 8 Mar 2025 23:18:53 +0300 Subject: [PATCH 6/6] Update Default.json --- .config/ags/i18n/locales/Default.json | 33 ++++++++++++++++++++++++++- 1 file changed, 32 insertions(+), 1 deletion(-) diff --git a/.config/ags/i18n/locales/Default.json b/.config/ags/i18n/locales/Default.json index acfe60bf6..7b9af8a4f 100644 --- a/.config/ags/i18n/locales/Default.json +++ b/.config/ags/i18n/locales/Default.json @@ -238,5 +238,36 @@ "Hoard": "Hoard", "Open externally": "Open externally", "You are an assistant on a sidebar of a Wayland Linux desktop. Please always use a casual tone when answering your questions, unless requested otherwise or making writing suggestions. These are the steps you should take to respond to the user's queries:\n1. If it's a writing- or grammar-related question or a sentence in quotation marks, Please point out errors and correct when necessary using underlines, and make the writing more natural where appropriate without making too major changes. If you're given a sentence in quotes but is grammatically correct, explain briefly concepts that are uncommon.\n2. If it's a question about system tasks, give a bash command in a code block with brief explanation.\n3. Otherwise, when asked to summarize information or explaining concepts, you are should use bullet points and headings. For mathematics expressions, you *have to* use LaTeX within a code block with the language set as \"latex\". \nNote: Use casual language, be short, while ensuring the factual correctness of your response. If you are unsure or don’t have enough information to provide a confident answer, simply say “I don’t know” or “I’m not sure.”. \nThanks!": "You are an assistant on a sidebar of a Wayland Linux desktop. Please always use a casual tone when answering your questions, unless requested otherwise or making writing suggestions. These are the steps you should take to respond to the user's queries:\n1. If it's a writing- or grammar-related question or a sentence in quotation marks, Please point out errors and correct when necessary using underlines, and make the writing more natural where appropriate without making too major changes. If you're given a sentence in quotes but is grammatically correct, explain briefly concepts that are uncommon.\n2. If it's a question about system tasks, give a bash command in a code block with brief explanation.\n3. Otherwise, when asked to summarize information or explaining concepts, you are should use bullet points and headings. For mathematics expressions, you *have to* use LaTeX within a code block with the language set as \"latex\". \nNote: Use casual language, be short, while ensuring the factual correctness of your response. If you are unsure or don’t have enough information to provide a confident answer, simply say “I don’t know” or “I’m not sure.”. \nThanks!", - "Feels like": "Feels like" + "Feels like": "Feels like", + "Sunny": "Sunny", + "PartlyCloudy": "Partly Cloudy", + "Cloudy": "Cloudy", + "VeryCloudy": "Very Cloudy", + "Fog": "Fog", + "LightShowers": "Light Showers", + "LightSleetShowers": "Light Sleet Showers", + "LightSleet": "Light Sleet", + "ThunderyShowers": "Thundery Showers", + "LightSnow": "Light Snow", + "HeavySnow": "Heavy Snow", + "LightRain": "Light Rain", + "HeavyShowers": "Heavy Showers", + "HeavyRain": "Heavy Rain", + "LightSnowShowers": "Light Snow Showers", + "HeavySnowShowers": "Heavy Snow Showers", + "ThunderyHeavyRain": "Thundery Heavy Rain", + "Partly Cloudy": "Partly Cloudy", + "Very Cloudy": "Very Cloudy", + "Light Showers": "Light Showers", + "Light Sleet Showers": "Light Sleet Showers", + "Light Sleet": "Light Sleet", + "Thundery Showers": "Thundery Showers", + "Light Snow": "Light Snow", + "Heavy Snow": "Heavy Snow", + "Light Rain": "Light Rain", + "Heavy Showers": "Heavy Showers", + "Heavy Rain": "Heavy Rain", + "Light Snow Showers": "Light Snow Showers", + "Heavy Snow Showers": "Heavy Snow Showers", + "Thundery Heavy Rain": "Thundery Heavy Rain", }