TRANSLATE

NOT DETERMINISTICALLY ASSERTABLE, and deliberately recorded as a probe rather than a support claim -- the same treatment batch D gave DETECTLANGUAGE, which is the same service behind the same disclaimer. Microsoft's page carries the Note box "This function is a service backed function. The supported languages and results may vary as languages are added or removed", and describes the function as translating "by using Microsoft Translation Services". THE PAGE PUBLISHES NO FORMULA/RESULT TABLE at all: its only example is prose, stating that =TRANSLATE(A1, "en", "es") on "Hello, World!" displays "Hola mundo!". Its four listed failure modes are properties of that service rather than of a spreadsheet engine, and NONE of them is given an error code -- "Text Too Long" ("You have too many characters in a cell"), "Error in Value" ("You have a non-text value in your cell"), "Invalid Language" ("You have entered an invalid language code or one we don't support") and "Request Throttled" ("You have exceeded your daily quota of the translation function"). No offline engine can reproduce "Hola mundo!", and an engine that DID return it from a local phrase table would not thereby be compatible with the documented service. What the run does establish is recorded separately: probing all four pinned LibreOffice builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3) with the plain name, the _xlfn. storage form, the COM.MICROSOFT. add-in form, the ORG.OPENOFFICE. form and the _xlfn.ORG.OPENOFFICE. form returned #NAME? for ALL FIVE spellings on every build, which is the signature of a name the engine does not implement at all. Microsoft's page was read live on 2026-08-31 at https://support.microsoft.com/en-us/excel/functions/translate-function. FETCH NOTE FOR THIS BATCH: batch F recorded every /en-us/office/<name>-function-<guid> URL returning Microsoft's 'Sorry, the page you're looking for can't be found' body; today BOTH paths serve the article again -- the GUID form redirects to /en-us/excel/functions/<slug>-function -- and every page cited in this batch came back complete (217-223 KB) in one or two attempts, with no 87 KB stub responses. Nothing here is sourced from a search snippet or a mirror.

NOT DETERMINISTICALLY ASSERTABLE, and deliberately recorded as a probe rather than a support claim -- the same treatment batch D gave DETECTLANGUAGE, which is the same service behind the same disclaimer. Microsoft's page carries the Note box "This function is a service backed function. The supported languages and results may vary as languages are added or removed", and describes the function as translating "by using Microsoft Translation Services". THE PAGE PUBLISHES NO FORMULA/RESULT TABLE at all: its only example is prose, stating that =TRANSLATE(A1, "en", "es") on "Hello, World!" displays "Hola mundo!". Its four listed failure modes are properties of that service rather than of a spreadsheet engine, and NONE of them is given an error code -- "Text Too Long" ("You have too many characters in a cell"), "Error in Value" ("You have a non-text value in your cell"), "Invalid Language" ("You have entered an invalid language code or one we don't support") and "Request Throttled" ("You have exceeded your daily quota of the translation function"). No offline engine can reproduce "Hola mundo!", and an engine that DID return it from a local phrase table would not thereby be compatible with the documented service. What the run does establish is recorded separately: probing all four pinned LibreOffice builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3) with the plain name, the _xlfn. storage form, the COM.MICROSOFT. add-in form, the ORG.OPENOFFICE. form and the _xlfn.ORG.OPENOFFICE. form returned #NAME? for ALL FIVE spellings on every build, which is the signature of a name the engine does not implement at all. Microsoft's page was read live on 2026-08-31 at https://support.microsoft.com/en-us/excel/functions/translate-function. FETCH NOTE FOR THIS BATCH: batch F recorded every /en-us/office/<name>-function-<guid> URL returning Microsoft's 'Sorry, the page you're looking for can't be found' body; today BOTH paths serve the article again -- the GUID form redirects to /en-us/excel/functions/<slug>-function -- and every page cited in this batch came back complete (217-223 KB) in one or two attempts, with no 87 KB stub responses. Nothing here is sourced from a search snippet or a mirror.

NOT DETERMINISTICALLY ASSERTABLE, and deliberately recorded as a probe rather than a support claim -- the same treatment batch D gave DETECTLANGUAGE, which is the same service behind the same disclaimer. Microsoft's page carries the Note box "This function is a service backed function. The supported languages and results may vary as languages are added or removed", and describes the function as translating "by using Microsoft Translation Services". THE PAGE PUBLISHES NO FORMULA/RESULT TABLE at all: its only example is prose, stating that =TRANSLATE(A1, "en", "es") on "Hello, World!" displays "Hola mundo!". Its four listed failure modes are properties of that service rather than of a spreadsheet engine, and NONE of them is given an error code -- "Text Too Long" ("You have too many characters in a cell"), "Error in Value" ("You have a non-text value in your cell"), "Invalid Language" ("You have entered an invalid language code or one we don't support") and "Request Throttled" ("You have exceeded your daily quota of the translation function"). No offline engine can reproduce "Hola mundo!", and an engine that DID return it from a local phrase table would not thereby be compatible with the documented service. What the run does establish is recorded separately: probing all four pinned LibreOffice builds (24.2.0.3, 24.8.7.2, 25.2.0.3, 25.8.7.3) with the plain name, the _xlfn. storage form, the COM.MICROSOFT. add-in form, the ORG.OPENOFFICE. form and the _xlfn.ORG.OPENOFFICE. form returned #NAME? for ALL FIVE spellings on every build, which is the signature of a name the engine does not implement at all. Microsoft's page was read live on 2026-08-31 at https://support.microsoft.com/en-us/excel/functions/translate-function. FETCH NOTE FOR THIS BATCH: batch F recorded every /en-us/office/<name>-function-<guid> URL returning Microsoft's 'Sorry, the page you're looking for can't be found' body; today BOTH paths serve the article again -- the GUID form redirects to /en-us/excel/functions/<slug>-function -- and every page cited in this batch came back complete (217-223 KB) in one or two attempts, with no 87 KB stub responses. Nothing here is sourced from a search snippet or a mirror.