How do you translate an ISO 660:2020 oil acid value report without confusing acid value in mg KOH/g, free fatty acid percentage, titration, acidity calculated as oleic acid and the pH of a liquid? Food laboratories, edible-oil importers, manufacturers, quality managers and technical translators searching for ISO 660 translation, vegetable oil acid value mg KOH/g, FFA percentage as oleic acid, oil acidity titration report and bilingual fat quality certificates need clear evidence rather than attractive but incorrect English equivalents. The number, the expression basis and the sample are one inseparable finding.
Acid value expresses how much potassium hydroxide is conventionally required per mass of fat or oil to neutralize the acidic constituents represented by the method. Acidity can also be reported through a conventional free-fatty-acid basis, but the two formats are not interchangeable numbers unless the reporting convention and conversion are identified. A high acid value is not itself a measured pH, a peroxide value, a proof of microbial contamination or a universal judgement that a food is unfit for consumption. Accurate translation therefore preserves the analytical quantity, its unit, the acid basis and the stated limitations of the method.
The ISO catalogue identifies ISO 660:2020 as the fourth edition of “Animal and vegetable fats and oils — Determination of acid value and acidity,” published March 2020 and confirmed in 2025. Its public abstract describes three methods, two titrimetric and one potentiometric, for determining acidity in covered fats and oils. The scope includes refined and crude animal or vegetable fats and oils, soap stock fatty acids and technical fatty acids; it excludes waxes and milk-related fats. ISO also notes that the methods are nonspecific for acid types and may include mineral acids if present. This article teaches translation of evidence; it is not a substitute for the licensed method or a food-safety determination.
This is a specialised article under Master Art of Translation, not a new general translation hub. Use the Vocabulary Learning Hub to develop conceptual chemical vocabulary and How English Works to study language equivalence. For the official scope and edition, refer to ISO 660:2020. The page owns only the narrow problem of interpreting acid-value and acidity results across languages.
1. Start with the chemical quantity, not a familiar word
1.1 Acid value is a defined laboratory quantity
An acid value is commonly expressed as milligrams of potassium hydroxide per gram of sample, written mg KOH/g. This unit is not merely a decoration that can be dropped from a report. It links a conventional neutralizing amount to a defined mass of oil or fat under the method. A source may use local names equivalent to “acid number,” “acid value” or “neutralization number.” The translator should follow the actual laboratory standard and legend, not assume that every use of “acid” in a food document refers to the same quantity.
A buyer may ask, “What is the acid of this olive oil?” The informal question could refer to free acidity, acid value, or another quality parameter. The translated laboratory certificate should retain the stated quantity and unit. If the source says 1.2 mg KOH/g, writing simply “acidity 1.2%” is a change of both unit and analytical basis. A precise English heading prevents mistakes before the reader even reaches the footnotes.
1.2 Free fatty acid percentage needs a declared reference acid
Free fatty acids are frequently reported as a percentage calculated on a conventional fatty-acid basis, such as oleic acid. Other oils or reporting standards may use a different named acid for the conversion. Therefore, “FFA 0.5%” is incomplete if the basis is necessary for a valid comparison and the report states it. Preserve the phrase “as oleic acid,” “as palmitic acid” or another actual basis. Do not silently substitute a common basis from a different oil category.
For example, a buyer’s spreadsheet may have a column called “FFA (% oleic),” while a laboratory certificate expresses acidity under another convention. The translator should not copy the number into that column without an authorized conversion. The source result and its calculation basis must remain visible. The appropriate action may be to add a separate field or to request a conversion from the qualified laboratory or technical owner.
1.3 “Acidity” in an oil report is not automatically pH
People often associate acidity with the pH scale, especially in aqueous solutions. Oil acid value is not simply the pH of the oil. A source language can use a word corresponding to “acidity,” but the surrounding method and units establish its technical meaning. Translating mg KOH/g as “pH units” or writing “pH 2.0” because a result value is 2.0 creates an entirely different property. The translator should read the method designation and measurement basis before selecting the English terminology.
A food product specification may contain both a pH field for an aqueous preparation and a free-acidity field for oil. They can appear in the same document without referring to the same test. Do not harmonize them under a single heading “acid content.” Distinguish each method, the sample matrix and the actual report unit. This makes the information usable for international quality teams with different linguistic habits.
1.4 Acid value is not peroxide value
Peroxide value is another common oil-quality measurement, but it concerns different chemical evidence associated with oxidation products and uses a different reporting basis. An acid value and a peroxide value are not interchangeable even when both help characterize oil quality. The standard ISO 660 belongs to acid-value and acidity determination, while another test may address peroxides. Keep the two result columns and reference methods distinct; one cannot be derived from the other’s number by merely changing units.
An import declaration might request both parameters. If the source certificate reports only acid value, the translator must not populate the peroxide field from the same number. Even a favorable acid value cannot guarantee a favorable peroxide value or comprehensive shelf-life performance. Every property needs its own evidence. This narrow distinction also prevents the present article from competing with the existing specialist guide to oil peroxide reports.
2. Read the ISO scope and method identity carefully
2.1 The ISO document covers several kinds of fats and oils
The public scope of ISO 660:2020 includes refined and crude vegetable or animal fats and oils, as well as certain fatty-acid materials such as soap stock fatty acids and technical fatty acids. A translator should preserve the actual sample class rather than assuming that every record concerns edible retail cooking oil. A technical fatty acid is not necessarily a consumer food ingredient. The title “animal and vegetable fats and oils” is a formal standard heading, not a declaration of the sample’s food grade.
Consider a document for a fatty-acid feedstock used in manufacturing. Rewriting it as an edible-oil quality certificate would change the intended material and potentially mislead a purchaser. Keep the material name, intended-use status where stated, sample ID and method. If the source does not identify end use, do not infer it from the presence of an ISO food-and-oil standard.
2.2 Waxes and dairy fats are outside the stated scope
The ISO public abstract excludes waxes and milk or milk-product fat from this document’s scope. A translated method statement should not imply that those excluded materials were validated under the same procedure unless another appropriate source establishes the basis. The exclusion does not mean that such substances lack measurable acidity; it means that this particular standard’s stated applicability does not extend to them as described. A translator must preserve that difference between the existence of a chemical property and the scope of one procedure.
A client may send an internal test sheet that labels a wax material “ISO 660” while the material appears outside the public scope. Translate the source citation faithfully but raise a technical query rather than altering it to look compliant. The laboratory or method owner must explain the intended procedure. A translated report is not an authorization to broaden a standard.
2.3 Two titrimetric and one potentiometric route are identified
The official catalogue describes three methods: two titrimetric and one potentiometric. This does not authorize an untrained translator to invent the specific steps, reagent concentrations or endpoint rules of a particular laboratory. In translation, the distinction matters because a report may identify which technique was used and what endpoint or measurement was recorded. Preserve that identifier as given. Do not replace “potentiometric” with “colour-change titration” merely because both methods concern acid determination.
A laboratory may use a procedure code and a method letter that are explained in its controlled documentation. When the English needs an expansion of that code, look for the approved legend rather than choosing one from a generic web article. The method’s public abstract establishes the broad categories, but the licensed document and laboratory records control actual procedural details. This prevents false claims of having observed laboratory steps that the translator never saw.
2.4 A standard’s publication year is not a sample test date
ISO 660:2020 identifies the 2020 edition. It does not say a sample was tested in 2020, that a laboratory used the latest edition, or that a report issued in 2026 necessarily followed every current requirement. Translate the standard edition, laboratory test date and report issue date separately. A revised certificate may list a different issue date without changing the original sample collection date. These distinctions keep report provenance intact.
A buyer’s procurement form may simply show “ISO 660” and an internal date. Ask whether the method edition is present in the source or in the laboratory’s technical record. Do not auto-complete the title from memory if the actual version is unknown. The correct translation may preserve the short citation and note that the edition requires confirmation. Uncertainty about provenance should be resolved, not hidden behind a precise-looking invented reference.
3. Understand the number and the underlying convention
3.1 mg KOH/g joins a reagent convention to sample mass
The common expression mg KOH/g represents milligrams of potassium hydroxide corresponding to the acid value per gram of material. It can look surprising to a nonchemist that an oil test refers to KOH rather than directly naming the fatty acids. The reason is that acid value is framed through neutralization equivalent. The translator should keep the actual unit and avoid paraphrasing it as “milligrams of acid per gram” without qualification; the two are not the same amount by mass.
A laboratory table might use an abbreviated heading such as AV (mg KOH/g). Preserve both the abbreviation and its meaning in a glossary. A spreadsheet that stores only the numeral loses the basis necessary to understand it. The source language’s grammatical order may differ, but the final English should clearly state which substance is the sample and what the numerical expression represents.
3.2 Converting to percent FFA needs chemistry, not typography
A free-fatty-acid percentage calculated from acid value depends on the molecular mass of the named reference fatty acid and the conversion convention. For a simple monocarboxylic fatty acid assumption, the stoichiometric relationship links neutralization equivalent to the mass of that reference acid. This is why percent FFA as oleic acid is not numerically equal to an acid value expressed in mg KOH/g. A translator should only report a calculated percentage when the source, specification or responsible analyst supplies the correct basis and computation.
As an illustrative classroom exercise, an acid value of 1 mg KOH/g corresponds to about 0.50% free fatty acids calculated as oleic acid under the usual one-acid-group assumption. This is a demonstration of units, not a laboratory result or a universal conversion for every acid mixture. A different reporting acid changes the factor. The translator must not apply a conversion to a commercial certificate without explicit technical authorization and appropriate rounding.
3.3 A non-specific method cannot identify each acid species
The ISO catalogue explicitly notes that the methods are nonspecific with respect to the types of acids present. They do not distinguish mineral acids from free fatty acids and other organic acids merely through the acid-value result. Therefore, a translated certificate must not state that all measured acidity was caused by a particular fatty acid unless another valid source identifies the composition. “Calculated as oleic acid” is a reporting convention, not proof that every acidic molecule in the sample was oleic acid.
This is a subtle but important linguistic trap. The phrase “oleic acidity” may be interpreted as the actual concentration of oleic acid, whereas a method may calculate acidity conventionally using oleic acid as the reference. Translate “expressed as” or “calculated as” when those qualifiers appear. They signal a measurement convention. Without them, the target-language report can accidentally assert a molecular identification that the method does not provide.
3.4 Mineral acids can contribute to the reported value
Because the methods are nonspecific, mineral acids present in a sample can contribute to the acid value. A translator should not imply that the reported value represents only fatty acids in every possible material. This distinction matters particularly for technical fatty acids, feedstocks or unusual samples. The standard’s scope and the sample’s known chemistry affect interpretation, but they do not permit unsupported partitioning of the result among different acidic constituents.
A factory quality team may ask for an English statement saying “free fatty acids are exactly X percent.” If the source only reports an acid value, an appropriate translation should use the stated method terminology and any provided conventional conversion. Further composition claims would require different analytical evidence or technical interpretation. A familiar word such as “free” must not remove the uncertainty that is intrinsic to a nonspecific assay.
4. Preserve titration language without inventing procedure details
4.1 Titrant, analyte and sample must stay in their roles
A titration report may describe the sample, the titrant, the endpoint and the amount used. These are not interchangeable components. The oil or fat is the tested material; the titrant is a reagent used in the analytical process; the endpoint is a condition used to determine the result under the method. Translate each role consistently. An incorrect English rendering can make it sound as though the oil was itself a potassium hydroxide solution or that the laboratory measured the mass of an isolated fatty acid.
Suppose a laboratory worksheet contains a titrant concentration and a sample mass. They must remain attached to their appropriate symbols and units. If the worksheet has an unfamiliar abbreviation, query its definition rather than assigning it to the most familiar chemical. Translators should build a field map showing the quantities, their units and their relationships before creating a polished narrative.
4.2 Visual endpoints and potentiometric endpoints are different descriptions
The public ISO abstract identifies titrimetric and potentiometric approaches. A source report may describe a visual endpoint or an instrumentally detected endpoint, depending on the method and laboratory. Do not generalize them into one unqualified “colour change” description. A potentiometric measurement is not simply a synonym for observing an indicator. Translate the recorded approach and any associated data fields without claiming a particular operational sequence that is not documented.
A technical reader may be concerned because a strongly coloured oil makes visual observation challenging. That concern can be discussed as context, but the translation should not declare that the laboratory used one method instead of another unless the report says so. If the method code is ambiguous, request the appropriate technical record. Method suitability and procedural details belong to the laboratory’s validated work, not the translator’s guess.
4.3 Blank corrections must not disappear in arithmetic summaries
Laboratory worksheets may include blank measurements and corrections in their data-processing record. If the source describes a blank or corrected titration volume, preserve the distinction. A translator who labels a corrected volume as the raw sample volume or deletes a footnote can make the calculation impossible to reconcile. The goal is not to reproduce every analytic formula from memory, but to ensure that the English refers to the same data items and computations as the source.
Imagine a worksheet with two columns for an observed volume and a corrected value. If a translated heading calls both “titrant volume,” the reader may use the wrong figure. Use clear labels such as “observed volume” and “blank-corrected volume” only where the source and laboratory convention support them. A technical reviewer should be able to trace each figure through the reported calculation without an invented intermediate step.
4.4 Apparatus notes are evidence about method application
A report may list a titrator identifier, a balance, reagent lot, calibration reference or analytical run. Such details are important for traceability but do not themselves prove analytical validity or product quality. Translate the actual identifiers without inserting missing calibration dates or implying an accredited scope that the source does not declare. The method name, instrument name and laboratory approval status are separate facts.
For international document use, a robust target-language report can preserve model numbers, reagent identifiers, run codes, quality-control flags and authorization signatures exactly. The explanatory words around them may change. If an abbreviation occurs only once with no legend, retain the code and request clarification when its meaning affects interpretation. Do not replace official instrument identifiers with a generic English term that would break the audit trail.
5. Interpret oil quality without overpromising
5.1 Acid value does not by itself measure oxidation state
Acid value and oxidation-related measurements can provide different information about an oil. A sample may exhibit a certain acid value without that number alone specifying peroxide concentration, volatile compounds, flavour or shelf life. Translate the acid-value result as acid value, not as a comprehensive oxidative stability index. If the source makes a broader claim, keep its attribution and ask what evidence supports it. A method-defined number must not be promoted into a universal quality judgement merely because buyers want a simple verdict.
A commercial certificate might include acid value and peroxide value as separate tests. Keep them in separate rows with their respective units and methods. If one is absent, do not calculate it from the other. The terms may be related in a broad quality discussion, but they describe distinct analytical questions. This matters when purchasing teams compare records from different suppliers and attempt to rank oils using one misleading combined “rancidity” score.
5.2 “Rancid” is a sensory or broader quality description
Rancidity is often associated with undesirable changes in fats, including hydrolytic and oxidative processes, but an acid-value result alone does not establish a complete sensory diagnosis. A translator may render the word “rancid” where it appears in the source, but should not add it as an interpretation of a number unless an authorized specification or report provides that conclusion. A laboratory measurement, a sensory panel and a commercial rejection decision are different kinds of evidence.
Consider an edible-oil buyer receiving a certificate with a moderate acid value and a short source-language comment that the result was within a named internal limit. The English should report the actual value and stated criterion, not declare that the oil “tastes fresh.” Taste was not measured by the acid-value method. Preserving those boundaries makes the report more useful, not less persuasive.
5.3 Product labels and laboratory results occupy different roles
Food labels may make nutritional, ingredient or marketing statements; laboratory acid-value reports provide analytical evidence for a sampled material. A translator should not turn a method result into an ingredient declaration or a nutrition fact. Free fatty acids do not necessarily map onto a label’s total fat composition in the way a casual reader imagines. Likewise, “acid value” should not be translated as “percentage of dietary acid.” The source’s measurement definition takes precedence over everyday connotations.
An importer may ask for one English paragraph suitable for a retail product page. Write it only after distinguishing what the laboratory can support from what the brand wishes to claim. If the source is a certificate, retain the data as technical evidence. Any marketing statement should undergo a separate substantiation and regulatory review, especially across jurisdictions where food-labelling rules differ.
5.4 Limits depend on the oil, grade and applicable specification
There is no single acid-value acceptance threshold supplied by the ISO method that determines the suitability of every fat or oil in every country. Product specifications can differ according to oil type, refining stage, intended use and applicable requirements. Translate a pass/fail judgement only if the source provides it and identify the named criterion. Do not invent a universal “safe below X” statement in an article or certificate.
For example, a crude feedstock and a refined retail oil may have different commercial targets. A value acceptable for one processing stage may be inappropriate as a specification for another, but the translator cannot decide that from ISO 660’s title. Keep the sample identity, result and contract criterion distinct, and refer product-release decisions to the responsible specialists. International readability should not come at the expense of invented regulatory certainty.
6. Keep sample identity, preparation and provenance clear
6.1 Crude and refined oil must not be merged
A crude oil, partially refined material and finished refined product can differ significantly in processing history and commercial use. A source laboratory may test more than one stage of a production process. Preserve the exact product description, lot, collection point and refining stage in translation. Calling every sample simply “vegetable oil” removes distinctions needed for traceability and evaluation. A source word that means raw or unrefined should not be silently omitted because it sounds less marketable in English.
Imagine a factory table reporting two values from the same production line before and after a processing stage. If both are labelled “final oil,” the reader loses the comparison. Keep the source sampling stage attached to each result. If the stage codes are internal, request an approved glossary or retain the codes with explanatory notes. The objective is to translate the evidence trail, not to tidy it into a product brochure.
6.2 Species and product origin can matter
Animal and vegetable fats and oils cover many source materials, but a laboratory acid-value report does not automatically authenticate origin or species. Translate the declared oil type, such as a named seed or fruit oil, without implying that the assay itself proves authenticity. Where the source uses a generic term, do not replace it with a popular oil category because the sample resembles one. Identity claims require their own source documentation and analytical support when relevant.
A shipment may carry a commercial product label, a batch certificate and a laboratory test record. The English should preserve who made each claim. “Supplier described the sample as X” differs from “laboratory identified the sample as X.” Even if the language is concise, the source attribution affects how a buyer can rely on the information.
6.3 Storage and sampling history are contextual information
Fats and oils may change during handling and storage. Reports can record sampling location, container, seal, received condition and dates. Translate these accurately while avoiding claims about what should have happened under a particular method unless the source establishes it. “Stored at ambient temperature” and “refrigerated” are not synonyms. Equally, the report’s issue date is not the same as the sampling or analysis date. Preserve chronology so the result remains tied to the material that was actually examined.
A buyer might compare an old certificate with a later shipment and assume the acid value is unchanged. The translator should retain the report’s date and lot identity rather than presenting it as an indefinite property of the product. A result is evidence about a defined sample at a relevant time, not a permanent guarantee for all future deliveries.
6.4 Report numbers and units are as important as grammatical fluency
Technical certificates commonly contain sample IDs, accession numbers, customer reference codes, analytical method numbers and authorized signatures. Preserve them precisely, including leading zeros. Translate the labels without reusing one code as another. A method reference and a batch number can look similar, but they identify different objects. A quality team should be able to reconcile the English version with the signed original through the same identifiers.
The same applies to units and punctuation. In one locale, “1,25” denotes one and a quarter; in another, a comma may be a thousands separator. Check the surrounding data and preserve the numeric value with an appropriate English decimal marker. A misplaced decimal point is not a stylistic issue: it can alter a quality judgement. The translator’s audit should include numbers and codes, not just terminology.
7. Fix common translation errors through worked examples
Example 1: Acid value becomes “acid percentage”
A laboratory certifies an acid value of 2.0 mg KOH/g, but the buyer’s translated spreadsheet displays “acidity 2.0%.” The error is not a slight wording change; it substitutes a percentage for a neutralization-based unit. Restore the original quantity and unit. If the client needs FFA percentage, obtain the declared reference acid and an authorized conversion. Label the derived result separately. The original 2.0 mg KOH/g must remain visible for audit.
Example 2: FFA percentage loses the “as oleic acid” qualifier
A certificate expresses acidity on an oleic-acid basis, and the translation says simply “oleic acid concentration.” That wording can imply direct chemical identification of oleic acid rather than a conventional calculation. Restore “acidity expressed as oleic acid” or the source’s technically equivalent formulation. Preserve the percentage and supporting method designation. If the result is used in a product specification, the conventional basis must remain explicit so that different oils are compared correctly.
Example 3: A potentiometric method is described as a colour test
The source identifies a potentiometric endpoint, but the English narrative says the laboratory watched for a visible colour change. That claim is unsupported and may contradict the actual method. Restore the source’s method category, preserve any instrument code and ask for clarification if the document is incomplete. The official standard’s abstract distinguishes method families; it does not permit a translator to invent the laboratory’s operating sequence.
Example 4: A crude oil is relabelled “refined cooking oil”
A supplier’s source file says the tested material was crude oil intended for further processing. A sales-facing English rewrite calls it ready-to-eat refined oil. Preserve the actual material and processing stage, along with lot and sampling identifiers. The acid-value result alone cannot establish food-grade suitability, completeness of refining or compliance with retail specifications. The translation should describe the evidence, leaving product classification and release decisions to separately supported records.
Example 5: Peroxide value is copied from acid value
A procurement template has two adjacent columns and a data operator copies an acid-value numeral into the peroxide field. The translator should catch the mismatch because the quantities have different meanings, units and analytical methods. Keep the actual acid-value result under ISO 660 and leave the peroxide field unreported unless separate evidence exists. Do not fabricate a zero or a conversion to fill a database. A missing measurement is preferable to a false one.
Example 6: A laboratory says “below criterion” without naming the criterion
The source contains a pass notation but the associated buyer limit appears on a separate specification. Translate the existing verdict without adding a universal rule. Identify the source of the criterion when it is part of the available record, and request it when the destination reader needs to evaluate the claim. A sentence such as “complies globally” should not be derived from a local or private buyer requirement. Keep method, number and criterion in separate fields.
Example 7: A technical fatty acid is marketed as edible fat
ISO 660’s scope includes certain technical fatty acids as well as edible-oil materials. A certificate for a manufacturing feedstock cannot automatically become an edible-oil certificate. Translate the material type and intended use exactly as declared. If the commercial document contains a contradictory description, flag it for the owner rather than reconciling it by rewriting the laboratory source. The standard’s name is not a guarantee of food suitability.
Example 8: The sample date is confused with the issue date
An oil shipment contains a sample collected weeks before the certificate was issued. An English summary uses the issue date as the date of testing and claims freshness at delivery. Restore each date to its recorded event: sampling, receipt, analysis and report release where available. Preserve the lot identity. No translation can establish the oil’s condition at a later destination date unless the source evidence supports that claim.
8. Four-week learning plan for technical translation teams
Week 1 — Build a chemical-quantity glossary
Start with the definitions of acid value, acidity, FFA, titrant, endpoint, sample mass, mineral acid and reporting basis. Write each term in plain English, then identify the exact source-language field it corresponds to. Create examples that distinguish mg KOH/g from percent calculated as a specified fatty acid. Ask a colleague to identify which expressions are laboratory measurements and which are conventional conversions. The learning goal is a system of related concepts, not memorization of isolated dictionary equivalents.
Week 2 — Practise units and conversion provenance
Use imaginary samples and calculate illustrative relationships between acid value and acidity as oleic acid. Document the reference fatty acid, assumptions and rounding. Then demonstrate what changes when the reporting basis is different. Compare this with pH and peroxide value to show why similar-looking quality words cannot be exchanged. Keep the exercises clearly labelled as hypothetical. A reviewer should be able to determine which value came from a source and which was derived for teaching.
Week 3 — Audit the method and sample scope
Prepare fictional certificates for refined vegetable oil, crude animal fat, technical fatty acids, wax and dairy-derived fat. Ask trainees which belong within the public ISO 660 scope and which should trigger a query. Add method headings referring to titrimetric and potentiometric approaches and ensure that translators do not invent procedural details. Practise distinguishing reported sample identity from inferred food-grade status. Each exercise should end with a short, reasoned source query rather than an unsupported correction to the source.
Week 4 — Produce a traceable bilingual certificate
Translate a de-identified oil test report containing a sample code, method edition, quantity, unit, expression basis, test and issue dates, method notes and any declared acceptance criteria. Ask a reviewer to reconstruct the original value and its meaning from the English alone. Look specifically for mislabelled percentages, omitted “as oleic acid” qualifiers, false peroxide substitutions, date errors and overstated pass claims. Archive the signed source, translation and resolved queries. Successful translation means a new reader can assess the evidence without inventing chemistry.
9. Frequently asked questions
What does ISO 660:2020 measure?
The official title concerns acid value and acidity in animal and vegetable fats and oils within the stated scope. It describes two titrimetric and one potentiometric method. A translated report should preserve the exact quantity, unit, material identity and declared result basis. The standard’s title does not establish every product’s commercial limit or food suitability, and its public abstract is not a laboratory procedure.
What does mg KOH/g mean?
It means milligrams of potassium hydroxide corresponding to the acid value per gram of the tested material. It is a conventional neutralization expression, not a direct statement that the sample contains that mass of potassium hydroxide. Translate the whole unit and keep it attached to the number. Removing it can cause readers to treat the result as a percentage or a different chemical concentration.
Are acid value and free fatty acid percentage identical?
No. They use different expressions, and conversion depends on the conventional reference acid and calculation basis. A report may give both, but a translator should preserve them separately. If converting is authorized, label the derived result, basis and rounding. Never copy an acid-value numeral directly into an FFA percentage column because the values happen to have similar magnitudes.
Does “as oleic acid” prove that the oil contains only oleic acid?
No. It may describe the conventional basis on which the acidity percentage is calculated. ISO notes that its methods are nonspecific as to acid species, so the result alone cannot identify or partition all acids present. The English should retain “expressed as” or “calculated as” where appropriate instead of claiming a direct molecular-composition measurement.
Is oil acid value the same as oil pH?
No. They describe different measurements and concepts. A report giving mg KOH/g should not be rewritten into pH units. If a specification contains a separate pH test, preserve its own method, matrix and result. Everyday language may call both “acidity,” but technical context determines what was actually measured.
Can acid value tell me whether an oil is rancid?
It may be relevant to a broader quality assessment, but it does not alone establish every oxidative, sensory or shelf-life property. Keep the reported value separate from peroxide value, flavour, microbiology and product-release decisions. If the source includes an attributed quality judgement, translate it accurately; do not invent one from the number alone.
Does ISO 660 include waxes or milk fats?
The public ISO scope excludes waxes and fat from milk or milk products. Do not imply that the stated method applies to those materials simply because their acidity can be discussed chemically. If a laboratory report appears to use the method outside its published scope, preserve the source citation and raise a technical question. The translator should not silently alter material identity or method status.
What if a report cites ISO 660 without a year?
Retain the source’s actual citation and request method-edition clarification where required. Do not automatically append 2020 just because it is the current edition in the official catalogue. The date a report was issued does not prove the edition used. Preserve laboratory test, sample and issue dates separately, and document uncertainty about method provenance.
Can a low acid value guarantee worldwide food compliance?
No. Commercial and legal acceptance criteria depend on oil type, intended use, market and applicable rules. A measurement method does not create a universal product-release threshold. Translate an existing criterion and decision with their attribution, but do not manufacture a broad compliance statement. A food-quality or regulatory specialist must make conclusions beyond the record.
What other eduKateSG resources support this topic?
For general translation design, consult Master Art of Translation. Use the protected Vocabulary Learning Hub for conceptual terminology and How English Works for meaning across languages. This guide is restricted to ISO 660 acid-value and acidity translation, so the larger resources retain their canonical roles.
10. Conclusion and official reference
Precise ISO 660 translation preserves acid value and acidity as defined quantities, retains mg KOH/g or the declared percentage basis, and prevents FFA, pH and peroxide value from collapsing into one vague “acid” concept. It also identifies the actual material and relevant method while avoiding unsupported judgments about rancidity, quality grade or food-law compliance. These are practical safeguards for laboratories, buyers and students who must read the same numerical evidence across languages.
Official reference: ISO 660:2020 — Animal and vegetable fats and oils, Determination of acid value and acidity. The ISO public catalogue verifies the edition, three-method scope, material applicability and non-specificity. This article does not reproduce licensed test instructions or replace a laboratory certificate, qualified analytical interpretation or jurisdiction-specific product decision.