Stay organized with collectionsSave and categorize content based on your preferences.
Avoid using slashes, except in code.
Slashes with dates
Don't use date formats that rely on slashes.
For information about how to write dates, seeDates and times.
Slashes with alternatives
Don't use slashes to separate alternatives.
Recommended: For example, a disaster
relief map is not subject to the usage limits even if it has been developed and
is hosted by a commercial entity.
Recommended: For example, a disaster
relief map is not subject to the usage limits even if it has been developed or
is hosted by a commercial entity.
Not recommended: For example, a disaster
relief map is not subject to the usage limits even if it has been
developed/hosted by a commercial entity.
Recommended: Call this method five or six
times.
Not recommended: Call this method 5/6
times.
And/or
Often,andimpliesor, so you don't need to write both words.
If you need to specify both in your content, avoid writingand/orexcept
when space is limited, such as in tables.
Recommended: You can view
and edit your own data.
Not recommended: You can
view and/or edit your own data.
Recommended: You can
export raw events, processed events, or both.
Not recommended: You can
export raw and/or processed events.
Slashes with file paths and URLs
Use forward slashes, as appropriate, in computer file paths and URLs.
Where very long URLs extend beyond a line, add a line break immediately after
a slash. Don't ever insert an extraneous hyphen into a URL to break it between two lines.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-15 UTC."],[[["\u003cp\u003eAvoid using slashes to denote alternatives, instead use "or" or "and" to ensure clarity.\u003c/p\u003e\n"],["\u003cp\u003eDo not use slashes in date formats, abbreviations (such as c/o or w/), or fractions; opt for clearer alternatives like dedicated date formats, spelled-out words, and decimals/percentages respectively.\u003c/p\u003e\n"],["\u003cp\u003eUse forward slashes appropriately in computer file paths and URLs (backslashes for Windows paths), and break long URLs after a forward slash.\u003c/p\u003e\n"],["\u003cp\u003eGenerally, replace slashes with "and" or "or" for better readability and to avoid ambiguity, except for code, file paths, and URLs where they have specific functions.\u003c/p\u003e\n"]]],["Avoid slashes in dates, alternatives, fractions, and abbreviations; spell out words instead. For alternatives, use \"or\" or \"and\" as needed. In fractions, use the proper fraction symbol, decimals, or percentages. For file paths and URLs, use forward slashes, and break long URLs after a slash. In Windows paths only use backslashes. In limited spaces, \"and/or\" can be used. Never use slashes to abbreviate words.\n"],null,["# Slashes\n\nAvoid using slashes, except in code.\n\nSlashes with dates\n------------------\n\nDon't use date formats that rely on slashes.\n\nFor information about how to write dates, see\n[Dates and times](/style/dates-times).\n\nSlashes with alternatives\n-------------------------\n\nDon't use slashes to separate alternatives.\n\nRecommended: For example, a disaster\nrelief map is not subject to the usage limits even if it has been developed and\nis hosted by a commercial entity.\n\nRecommended: For example, a disaster\nrelief map is not subject to the usage limits even if it has been developed or\nis hosted by a commercial entity.\n\nNot recommended: For example, a disaster\nrelief map is not subject to the usage limits even if it has been\ndeveloped/hosted by a commercial entity.\n\nRecommended: Call this method five or six\ntimes.\n\nNot recommended: Call this method 5/6\ntimes.\n\n### And/or\n\nOften, *and* implies *or* , so you don't need to write both words.\nIf you need to specify both in your content, avoid writing *and/or* except\nwhen space is limited, such as in tables.\n\nRecommended: You can view\nand edit your own data.\n\nNot recommended: You can\nview and/or edit your own data.\n\nRecommended: You can\nexport raw events, processed events, or both.\n\nNot recommended: You can\nexport raw and/or processed events.\n\nSlashes with file paths and URLs\n--------------------------------\n\nUse forward slashes, as appropriate, in computer file paths and URLs.\n| **Note**: If you're documenting a Windows path, use backslashes.\n\nRecommended:\nhttps://developers.google.com/cardboard/\n\nWhere very long URLs extend beyond a line, add a line break immediately after\na slash. Don't ever insert an extraneous hyphen into a URL to break it between two lines. \nRecommended:\nhttps://developers.google.com/\n\ncardboard/\n\nSlashes with fractions\n----------------------\n\nDon't use slashes with fractions because they can be ambiguous.\n\nIn the following example, 3/4 could be interpreted either as three-quarters\nor as stating that 4 is an alternative to 3.\n\nRecommended: ¾\n\nRecommended: 0.75\n\nRecommended: 75%\n\nNot recommended: 3/4\n\nSlashes with abbreviations\n--------------------------\n\nDon't use abbreviations that rely on slashes. Instead, spell the words out.\n\nRecommended: care of, with\n\nNot recommended: c/o, w/"]]
