#Translation Errors In zh-cn.rules (Simplified Chinese)

48 messages · Page 1 of 1 (latest)

azure osprey
#

I. Stats

  1. FireChanceFmt = "<white>开始开火：</white> <good>{0:0}%</good><gray> 机会/单元</gray>"
    Original: Starts Fires: 40% chance/tile
    Be like now: Opening Fire: 40% chance/unit
    Should be: "<white>点燃概率：</white> <good>{0:0}%</good><gray> 几率/格</gray>"
  2. HPFmt = "<white>攻击点数：</white> <good>{0:n0}</good>"
    Original: Hit Points: 4000
    Be like now: Attacking Points: 4000
    Should be: "<white>耐久：</white> <good>{0:n0}</good>"
  3. PenResistFmt = "<white>防渗透：</white> <good>-{0}</good> <gray>米</gray>"
    & PenetrationFmt = "<white>渗透:</white> <good>{0:0.##}</good> <gray>米</gray>"
    & ShieldPenResistFmt = "<white>护盾防渗透：</white> <good>-{0}</good> <gray>米</gray>"
    & ShieldPenetrationFmt = "<white>防御盾渗透：</white> <good>{0:.##}</good> <gray>防御盾</gray>"
    & ShieldDamageFmt = "<white>伤害vs防御盾:</white> <good>{0:n0}</good><gray>/发 (</gray><good>{1:n0}</good><gray>/秒)</gray>"
    Original: Penetration Resist: -4 meters
    & Penetration: 5 meters
    & Shield Pen. Resist: -25 meters
    & Shield Penetration: 2 shields
    & Dmg vs Shields: 2,250/shot (4,500/sec)
    Be like now: Infiltration Resist: -4 meters
    & Infiltration: 5 meters
    & Shield Inf. Resist: -25 meters
    & Defensive Shields Infiltration: 2 shields
    & Dmg vs Defendive Shields: 2,250/shot (4,500/sec)
    Should be: "<white>抗穿透：</white> <good>-{0}</good> <gray>米</gray>"
    & "<white>穿透：</white> <good>{0:0.##}</good> <gray>米</gray>"
    & "<white>护盾抗穿透：</white> <good>-{0}</good> <gray>米</gray>"
    & "<white>护盾穿透：</white> <good>{0:.##}</good> <gray>面护盾</gray>"
    & "<white>对护盾伤害：</white> <good>{0:n0}</good><gray>/发 (</gray><good>{1:n0}</good><gray>/秒)</gray>"
  4. PowerUsageContinuousMinutesFmt = "<white>电力消耗：</white> <good>{0:0.##}</good><gray>/秒</gray>"
    Original: Power Use: 1/min
    Be like now: Power Use: 1/sec
    Should be: <white>电力消耗：</white> <good>{0:0.##}</good><gray>/分钟</gray>"
  5. RailgunBuffFmt = "<gray>轨道枪的……
    Original: ...railgun...
    Be like now: ...railrifle...
    Should be: "<gray>轨道炮的……

And More...

#

  1. SalvoFmt = "<white>打捞：</white> <good>{0:0.##}</good> <gray>发/</gray><good>{1:0.##}</good> <gray>秒</gray>"
    Original: Salvo: 1 shots/0.25 sec
    Be like now: Salvage: 1 shots/0.25 sec
    Should be: "<white>连射：</white> <good>{0:0.##}</good> <gray>发/</gray><good>{1:0.##}</good> <gray>秒</gray>"

  2. SeparationRangeFmt = "<white>分离：</white> <good>{0:0}</good> <gray>米</gray>"
    Original: Separation: 23 meters
    Be like now: Separating: 23 meters
    Should be: "<white>间隔：</white> <good>{0:0}</good> <gray>米</gray>"

  3. ShotDamageFmt = "<white>伤害vs射击:</white> <good>{0:n0}</good><gray>/发 (</gray><good>{1:n0}</good><gray>/秒)</gray>"
    Original: Dmg vs Shots: 1,800/shots (7,200/sec)
    Be like now: Damaging vs Shooting: 1,800/shots (7,200/sec)
    Should be: "<white>对弹丸伤害：</white> <good>{0:n0}</good><gray>/发 (</gray><good>{1:n0}</good><gray>/秒)</gray>"

  4. ShotHPFmt = "<white>持续时间：</white> <good>{0:n0}</good>"
    Original: Durability: 125
    Be like now: Duration: 125
    Should be: "<white>弹丸耐久：</white> <good>{0:n0}</good>"

  5. StretchRangeFmt = "<white>延伸范围：</white> <good>{0:0}</good> <gray>米</gray>"
    Original: Stretch Range: 600 meters
    Be like now: Extension Range: 600 meters
    Should be: "<white>拉伸范围：</white> <good>{0:0}</good> <gray>米</gray>"

And More...

azure osprey
#

II. ArenaModeConfig/Rulesets

  1. FFA1500K = "所有人免费- 1.5M"
    & FFA1500KShort = ""
    & FFA3000K = "所有人免费- 3M"
    & FFA3000KShort = ""
    & FFA500K = "所有人免费 - 500 K"
    & FFA500KShort = ""
    Original: Free For All - 1.5M
    & FFA\n1.5M
    & Free For All - 3M
    & FFA\n3M
    & Free For All - 500K
    & FFA\n500K
    Be like now: No Cost For Everyone - 1.5M
    & (Unchanged)
    & No Cost For Everyone - 3M
    & (Unchanged)
    & No Cost For Everyone - 500K
    & (Unchanged)
    Should be: 自由交战-1.5M
    & 混战\n1.5M
    & 自由交战-3M
    & 混战\n3M
    & 自由交战-500K
    & 混战\n500K

III. Brushes

  1. Block10x10 = 10x10区
    & Block1x1 = 1x1区
    & ……
    & Block9x9 = 9x9区
    Original: 10x10 Block
    & 1x1 Block
    & ...
    & 9x9 Block
    Be like now: 10x10 Area
    & 1x1 Area
    & ...
    & 9x9 Area
    Should be: 10x10方块
    & 1x1方块
    & ……
    & 9x9方块

  2. Box = 框
    & BoxIcon = 框
    Original: Box
    & Box
    Be like now: Frame
    & Frame
    Should be: 矩形
    & 矩形

IV. BuildBox

  1. InsufficientResourcesFmt = "不足{0}"
    Original: INSUFFICIENT {0}
    Be like now: (We can understand, but it's not a normal word order.)
    Should be: "{0}不足"

V. CareerMode

  1. MissionCompleted = 已完成任务
    & MissionFailed = 失败任务
    Original: MISSION COMPLETED
    & MISSION FAILED
    Be like now: (Same as the previous one, it's not a normal word order.)
    Should be: "任务完成"
    & "任务失败"

And More...

azure osprey
#

VI. CareerModeConfig

16.CombatDifficultyTip = 与敌舰的战斗非常具有挑战性。将鼠标光标悬停在每个选项上以了解详情。
Original: How challenging the combat versus enemy ships will be. Hover the mouse cursor over each option for details.
Be like now: Fighting enemy ships is very challenging. Hover the mouse cursor over each option for details.
Should be: "调整与敌舰战斗的挑战性。将鼠标光标悬停在每个选项上以了解详情。"

  1. DescriptionMP = ……，与流氓派别作战，……
    Original: ..., fighting rogue factions, ...
    Be like now: ..., fighting rascal factions, ...
    Should be: (In fact, I have no idea about the exact meaning of this sentense.)

VIII. CreativeMode

  1. Junk = 垃圾
    & JunkTip = 废弃战舰不与任何其他战舰为敌，但处在火线上时可以消耗。
    Original: Junk
    & Junk ships are not enemies with any other ships, but are considered expendable when in the line of fire.
    Be like now: (The expression is not unified.)
    & Abandoned ships are not enemies with any other ships, but can be consumed when in the line of fire.
    Should be: 废弃
    & "废弃战舰不与任何其他战舰为敌，但处在火线上时不能幸免于难。"

  2. Tween = 双方：
    & EaseIn = 加速
    & EaseInOut = 加速/减速
    & EaseOut = 减速
    Original: Tween:
    & Ease In
    & Ease In/Out
    & Ease Out
    Be like now: Twin:
    & Hasten
    & Hasten / Slow down
    & Slow down
    Should be: 补间：
    & 缓入
    & 缓入/缓出
    & 缓出

IX. CrewTransfer

  1. Failure = 你请求船员无法全部转移。……
    Original: Not all of the requested crew could be transferred. ...
    Be like now: You requested crew could not be all transferred. ...
    Should be: "您请求的船员无法全部转移。……"

And More...

azure osprey
#

X. DominationMode

  1. CapturePointNames
    {
    A字
    ……
    Z字
    }
    Original:
    {
    "Alpha"
    ...
    "Zeta"
    }
    Be like now:
    {
    A word
    ...
    Z word
    }
    Should be:
    {
    "A点"
    ……
    "Z点"
    }

  2. HomeCircleRequiredTip = 必须在家庭生成区内。
    Original: Must be within the home spawn area.
    Be like now: Must be within the family spawn area.
    Should be: "必须在锚地生成区内。"

XI. EconDifficulty

  1. Fast = 建造者
    & FreeBuild = 想象者（自由建造）
    & Normal = 建筑师
    & Slow = 造星者
    Original: Builder
    & Imagineer (Free Build)
    & Architect
    & Starwright
    Be like now: (In fact these items are correct, but I don't consider them to have flavor, especially the original name of this game, Starwright. So I propose my own scheme here, just for reference.)
    Should be: "造船能手"
    & "天马行空（自由建造）"
    & "设计大师"
    & "星舰巨匠"

XII. EditorGroups

  1. Utilities = 公共设施
    Original: Utilities
    Be like now: Public facilities
    Should be: "特种装备"

XIII. Formations

  1. Alpha = A字编队
    & Bravo = B字编队
    & Charlie = C字编队
    & Claw = 爪形编队
    & Delta = D字编队
    & Echo = E字编队
    & Foxtrot = F字编队
    & Gamma = G字编队
    Original: Alpha Formation
    & Bravo Formation
    & Charlie Formation
    & Claw Formation
    & Delta Formation
    & Echo Formation
    & Foxtrot Formation
    & Gamma Formation
    Be like now: A-word Formation
    & B-word Formation
    & C-word Formation
    & Paw Formation
    & D-word Formation
    & E-word Formation
    & F-word Formation
    & G-word Formation
    Should be: A号编队
    & B号编队
    & C号编队
    & 钳形编队
    & D号编队
    & E号编队
    & F号编队
    & G号编队

And More...

azure osprey
#

XIV. GameSetupScreen

  1. ReadyTip = 让其他玩家指导你准备开始你游戏！……
    Original: Lets the other players know that you are ready to start the game! ...
    Be like now: Lets the other players instruct you to prepare to start you game! ...
    Should be: "让其他玩家知道你准备好开始游戏！……"

XV. Hud

  1. AbandonShipTip = 指示所有船员在可能的情况下离战舰。
    Original: Instructs all crew to leave the ship if possible.
    Be like now: Instructs all crew to lea the ship if possible.
    Should be: 指示所有船员尽可能离开战舰。

  2. SpeedHalfLong = "缓慢(½ - M.P.标准)"
    Original: Slow (½ - M.P. Standard)
    Be like now: (The phrase M.P. is unchanged in text.)
    Should be: "缓慢(½ - 多人游戏标准)"

  3. WeaponBindings = 直接控制绑定
    Original: Direct Control Binding
    Be like now: Direct Control Bundle
    Should be: 直接控制按键

XVI. Inputs

  1. DirectControlFireWeaponsFmt = "直接控制：武器绑定#{0}"
    Original: Direct Control: Weapon Binding #{0}
    Be like now: Direct Control: Weapon Bundle #{0}
    Should be: "直接控制：武器按键#{0}"

And More...

azure osprey
#

  1. DirectControlToggleFaceCursor = 直接控制：切换自动面部光标
    Original: Direct Control: Toggle Auto Face Cursor
    Be like now: Direct Control: Toggle Auto Facial Cursor
    Should be: "直接控制：切换自动朝向光标"

  2. NumPad0 = 数字区0
    & ……
    & NumPadSlash = 数字区破折号
    & NumPadStar = 数字区星号
    Original: Num Pad 0
    & ...
    & Num Pad Slash
    & Num Pad Star
    Be like now: Num Area 0
    & ...
    & Num Area Dash
    & Num Area Star
    Should be: "小键盘0"
    & ……
    & "小键盘斜杠"
    & "小键盘星号"

  3. ShowScoreboard = 显示Scoreboard
    Original: Show Scoreboard
    Be like now: (The word Scoreboard is unchanged in text.)
    Should be: "显示计分板"

  4. launch_mines = 发射矿能
    Original: Launch Mines
    Be like now: Launch Ore Energy
    Should be: "发射地雷"

  5. missile_type_nuke = 发射器类型：核能
    Original: Launcher Type: Nuke
    Be like now: Launcher Type: Nuclear Energy
    Should be: "发射器类型：核武"

And More...

#

Translation Errors In zh-cn.rules (Simplified Chinese)

azure osprey
#

XVII. Jobs

  1. RefillO2 = 重复性氧气罐
    Original: Refilling Oxygen Tank
    Be like now: Repeatable Oxygen Tank
    Should be: "装填氧气罐"

XVIII. Lore

  1. Cabal
    {
    Title = 索尔党
    ……索尔……索尔星……党国……
    }
    Original:
    {
    Title = "Cabal of Sol"
    ...Sol...star Sol...Cabal...
    }
    Be like now:
    {
    Title = Party of Sol
    (I have 2 reasons for listing this as a translation error. First, Cabal of Sol is not about PARTY(党), but about RELIGION(教). Second, the name Sol is from Roman mythology, which is not familiar to most native Chinese speakers, and there are more general expressions to describe Earth's star in Chinese.)
    }
    Should be:
    {
    Title = "太阳神教"
    ……太阳……太阳……教国……
    (If the word "太阳" is not flavorful enough, other choises are "羲和", "东君" and "金乌", etc. Such as: "金乌教国" .)
    }

  2. Monolith/Lore2 = ……在索尔（地球）系小行星带……
    Original: ...within the Sol (Earth) system's asteroid belt...
    Be like now: (Same reason as above one.)
    Should be: ……在太阳系（地球所在）小行星带……

XIX. Parts

  1. LaserBlasterLargeDesc = 在一个炮塔上有两把大型激光枪，两把结合在一起，以牺牲一些准确性和多功能性为代价，获得了更高的伤害。
    Original: Pairs together two large laser guns on a single turret, which combine for much higher damage at the expense of some accuracy and versatility.
    Be like now: Pairs together two large laser rifles on a single turret, which combine for higher damage at the expense of some accuracy and versatility.
    Should be: "在一个炮塔上联装两座大型激光炮，以牺牲一些精度与泛用性为代价，合二为一取得了高得多的伤害。"

  2. ThrusterHuge = 超大推进器
    & ThrusterHugeIcon = 超大推进器
    Original: Huge Thruster
    & (The Same)
    Be like now: Oversized Thruster
    Should be: "巨型推进器"

And More...

azure osprey
#

XX. PvpModeConfig

  1. PerimeterDistances/NearFmt = "附近（{0}米）"
    Original: Near ({0} meters)
    Be like now: Nearby ({0} meters)
    Should be: "近（{0}米）"

  2. TeamsFfa = 所有人免费
    Original: Free For All
    Be like now: No Cost For Everyone
    Should be: "自由交战"

XXI. ReputationTitles

  1. ReputationTitles/5 = 联军
    Original: "Associate"
    Be like now: Alliance
    Should be: "伙伴"

XXII. Resource

  1. Battery = 炮组
    Original: Battery
    Be like now: Artillery crew
    Should be: "电池"

  2. TristeelPlural = 钛钢
    & TritaniumPlural = 钛
    Original: &Tristeel (= "Tri-\u200bSteel")
    & &Tritanium (= "Tritanium")
    Be like now: Ti-Steel
    & Titanium
    Should be: "三钛钢"
    & "三钛原矿"

And More...

azure osprey
#

XXIII. ResourceTransfer

  1. Failure = ……这通常是因为没有气闸允许船员获得待转移至目的地的资源的权限。
    Original: ...This is usually because there are no airlocks allowing crew access to the resources being transfered or their destination.
    Be like now: ...This is usually because there are no airlocks allowing crew to gain authority to the resources to be transferred to the destination.
    Should be: "……这通常是因为没有气闸允许船员取得通路前往待转移资源或其目的地。"

Here are two items that were missed:
IV. BuildBox

  1. NoCrewAccess = "<bad>✘ 无船员权限</bad>"
    & NoResourceAccessFmt = "<bad>✘ 无{0}权限</bad>"
    Original: <bad>✘ No Crew Access</bad>
    & <bad>✘ No {0} Access</bad>
    Be like now: <bad>✘ No Crew Authority</bad>
    & <bad>✘ No {0} Authority</bad>
    Should be: "<bad>✘ 无船员通路</bad>"
    & "<bad>✘ 无{0}通路</bad>"

XXIV. ResourcesBox

  1. AddSupplyLineTip = "<color r='50' g='149' b='255'>添加供应环节\n(<btn id='Game.Command'/>)</color>"
    & ClearAllSupplyTargets = 清除所有供应环节
    Original: <color r='50' g='149' b='255'>Add Supply Link\n(<btn id='Game.Command'/>)</color>
    & Clear All Supply Links
    Be like now: <color r='50' g='149' b='255'>Add Supply Aspect\n(<btn id='Game.Command'/>)</color>
    & Clear All Supply Aspects
    Should be: "<color r='50' g='149' b='255'>添加供应链\n(<btn id='Game.Command'/>)</color>"
    & "清除所有供应链"

XXV. Settings

  1. CopyGalaxySeed = 复制Galaxy种子
    & GalaxySeedFmt = "Galaxy种子:<b>{0}</b>"
    Original: Copy Galaxy Seed
    & Galaxy Seed: <b>{0}</b>
    Be like now: (The word Galaxy is unchanged in text.)
    Should be: "复制星系种子"
    & "星系种子：<b>{0}</b>"

  2. DirectControlShowWeaponCoverage = 显示发射弧线
    & DirectControlShowWeaponCoverageTip = ……将显示武器的发射弧线。
    Original: Show Firing Arcs
    & ...weapon firing arcs will be shown...
    Be like now: Show Launching Parabola
    & ...weapon lauching parabola will be shown...
    Should be: "显示射界弧度"
    & "……将显示武器的射界弧度。"

And more, but I'm going to sleep Zzz...

novel mantle
#

this is some dedication, sleep well

balmy sorrel
#

yea
Walt will be happy to know this stuff

azure osprey
#

  1. Gameplay/InterfaceLbl = 接口
    & Audio/InterfaceVol = 接口音量
    Original: Interface
    & Interface Vol.
    Be like now: (Still interface, but not about GUI.)
    Should be: "界面"
    & "界面音量"

  2. Gameplay/MultiplayerLbl = ""
    Original: Multiplayer
    Be like now: (Unchanged)
    Should be: "多人游戏"

  3. Gameplay/OverlaysLbl = 信息覆载
    Original: Informational Overlays
    Be like now: Information Override
    Should be: "信息叠层"

  4. GifRecorder/Framerate2 = " 每秒帧数"
    Original: frames per second
    Be like now: (It's correct, but looks a little weird in context.)
    Should be: " 帧每秒"

Here is an item that was missed:
55. SaveMedia/Framerate2 = ""
Original: " F.P.S."
Be like now: (Unchanged)
Should be: " 帧每秒"

And More...

azure osprey
#

  1. Graphics/BackgroundGridLines = 横线
    Original: Lines
    Be like now: Horizontal Lines
    Should be: "实线"

  2. Graphics/VSync = ""
    Original: VSync
    Be like now: (Unchanged)
    Should be: "垂直同步"

  3. Gameplay/PreferShipRelativeAttackAngle = 偏好战舰相对的攻击角度
    & Gameplay/PreferShipRelativeAttackAngleTip = "如果勾选，在敌舰上点击右键并拖动将使用相对于敌舰的攻击角度，而不是背景网格。按住<btn id='Game.ShipRelativeAttackAngle'/>来使用其他模式。"
    Original: PreferWorldRelativeAttackAngle = "Prefer Grid-Relative Attack Angles"
    & PreferWorldRelativeAttackAngleTip = "If checked, right-clicking and dragging on an enemy ship will use an attack angle relative to the background grid instead of the enemy ship. Hold <btn id='Game.WorldRelativeFollowAngle'/> to use the other mode."
    Be like now: (Wrong item names, seem to be from old version.)
    Should be: PreferWorldRelativeAttackAngle = "偏好网格相对的攻击角度"
    & PreferWorldRelativeAttackAngleTip = "如果勾选，在敌舰上点击右键并拖动将使用相对于背景网格的攻击角度，而不是敌舰。按住<btn id='Game.WorldRelativeFollowAngle'/>可以使用另一模式。"

  4. Gameplay/PreferWorldRelativeFollowAngleTip = "……可以使用其他模式。"
    Original: ...to use the other mode.
    Be like now: ...to use other modes.
    Should be: "……可以使用另一模式。"

  5. Designer/GrabLeavesCorridors = 抓手离开走廊
    Original: Grab Leaves Corridors
    Be like now: Grab Gets Away From Corridors
    Should be: "抓取留下走廊"

And More...

azure osprey
#

  1. Graphics/PlanetResolutionScale = Planet分辨率：
    Original: Planet Resolution
    Be like now: (The word Planet is unchanged in text.)
    Should be: "星球分辨率："

  2. Misc/DesyncDebugging
    & Misc/DesyncDebuggingTip
    & Misc/MaxSendRate
    & Misc/MaxSendRateTip
    Original: Enable Desync Debugging
    & If checked, then desync debugging will be enabled when hosting a multiplayer game. This will generate .rec files with extra info that will help the developer debug multiplayer desyncs, but performance will be somewhat reduced. If you get a desync, please send the .rec file in your Cosmoteer logs folder to the developer.
    & Max Send Rate (KBps)
    & The maximum rate at which network data can be sent, measured in kilobytes per second.
    Be like now: (These items simply do not exist in zh-cn.rules.)
    Should be: "启用不同步调试"
    & "如果勾选，则在主持多人游戏时将启用不同步调试。这将生成包含额外信息的.rec文件，这些信息将帮助开发人员解决多人游戏不同步问题，但游戏性能会有所降低。如果您遭遇了不同步，请将Cosmoteer日志文件夹中的.rec文件发送给开发人员。"
    & "最大发送速率(KB/s)"
    & "可以发送网络数据的最大速率，以千字节/秒为单位。"

  3. RevertSettings = 翻转
    Original: Revert
    Be like now: Invert
    Should be: "恢复"

  4. Saves/AutoSaveEvery = "每一 "
    & AutoSavesToKeep2 = " 最近的自动保存文件。"
    & LostShipsToKeep2 = " 最近的丢失战舰文件。"
    & QuickSavesToKeep2 = " 最近的快速保存文件。"
    Original: Every
    & most-recent Auto-Save files.
    & Save Lost Ship Designs
    & most-recent Quick-Save files.
    Be like now: (They look a little weird in context.)
    Should be: " 每"
    & " 个最近的自动保存文件。"
    & " 个最近的丢失战舰文件。"
    & " 个最近的快速保存文件。"

XXVI. ShipClasses

  1. Terran = 类地球
    & Ancient = 古代
    Original: Terran
    & (On the contrary, this item is not in en.rules.)
    Be like now: Earth-like
    & Ancient
    Should be: 人族
    & (Just delete it I think.)

And More...

azure osprey
#

XXVII. ShipLibraries

  1. Lost = 损失的战舰
    Original: Lost Ships
    Be like now: (Ununified expression.)
    Should be: "丢失的战舰"

XXVIII. ShipLibrary

  1. SortMode/CostHigh = "<img name='sort'/> 成本（高）。"
    & SortMode/CostLow = "<img name='sort'/> 成本（低）。"
    Original: <img name='sort'/> Cost (High)
    & <img name='sort'/> Cost (Low)
    Be like now: (Periods are weird.)
    Should be: "<img name='sort'/> 成本（高）"
    & "<img name='sort'/> 成本（低）"

XXIX. StatCategories

  1. DisruptorBolt = 扰乱器螺栓
    & LaserBoltLarge = 重型激光螺栓
    & LaserBoltSmall = 激光螺栓
    Original: Disruptor Bolt
    & Heavy Laser Bolt
    & Laser Bolt
    Be like now: Disruptor Screw
    & Heavy Laser Screw
    & Laser Screw
    Should be: "扰乱器脉冲"
    & "重型激光脉冲"
    & "激光脉冲"

  2. MissileNuke = 战略核导弹
    & Flak = 高射炮
    Original: Tactical Nuclear Missile
    & Flak
    Be like now: Strategic nuclear missiles
    & Flak Cannon
    Should be: "战术核导弹"
    & "高射炮弹"

XXX. TitleScreen

  1. Discord = 纷争
    Original: Discord
    Be like now: (Since it is the name of the platform, then I think it should keep unchanged.)
    Should be: ""

And More...

#
  1. Multiplayer = ""
    Original: MULTIPLAYER
    Be like now: (Unchanged)
    Should be: "多人游戏"

And more?
Temporarily no more. Those are all I've found in zh-cn.rules. I will continue to feeback if I find more.

azure osprey
#

How can I change the section of a post dudes??Fustration I just discovered that ideas-and-feedback section have the tag Translation!

plucky trench
#

don't worry about it, bug reports is fine

full sun
#

Small guide to our friend’s proposed fixes:
Original = text in English localization
Be like now = current actual translations (back into English) from Chinese localization
Should be = proposed Chinese translation

#

Looking over them currently! He has solid translations so far, I’ll give minor feedback if I see anything that I might disagree with

full sun
#

  1. should be: 与离群派别作战 (yeah this one was hard, lemme know if it makes sense! it’s better than leaving in “rascals” anyways)

  2. nothing of disagreement, I just wanna say that I love the translation lol

  3. I’ll disagree with this one, lemme know your thoughts:
    Should be: “直接控制：武器绑定#{0}键”

  4. 地雷 means landmine, have we been calling all of them landmines? I’ll go with whatever keeps consistency, whether that’s naval or land mine.

  5. 核武 or 核弹, which one sounds cooler to you? I think both fits for “nukes”

  6. I had gripes with what Cabal’s called in Chinese too, it just sounds like an anglicized political faction at first glance. I was thinking “光之教徒” (followers of light) as a name, though that does lose the conspiracy connotations that comes with Cabal. It should be a whole debate with Walt’s involvement I feel, not just left up to the paid translator’s opinion imo. But yeah! My interpretation of the broken words is: 太阳……星……阳……教国……
    But yeah, I like your original suggestion of 太阳神教, or 金乌教国. The latter might need your explanation though since I don’t get it fully, but it does sound cool and somewhat closer to consistency with “cabal”.

  7. Yeah the problem with renaming Sol (索尔) is that 太阳系 (the real name for our solar system) sounds pretty plain. we can maybe mix both translations to be 在索尔系（地球所在）小行星带……

cont’d

full sun
#

  1. 泛用性-> 通用性 perhaps?

  2. I think titanium steel sounds better/cooler than tritanium steel (as it is in Chinese), I’m inclined to let this one slide; your call though!

  3. should be: 抓取会留下走廊 (I added a “will” in there, for clarity. not sure if it breaks consistency.)

  4. I might be partial, but I like it being “earth-like” as opposed to “human race”

  5. 脉冲 means pulse, and while I do think it sounds better than screws, we literally call EMP missiles just EMP导弹 the last time I checked. Maybe we can keep the names as “screws” here, and rename EMP missiles to 电磁脉冲导弹. (EMP stands for electromagnetic pulse.)

#

Overall great stuff! One request for you man, can you find out what we can call Hyper- anything? I think 超感跳跃 doesn’t sound very cool, and anything hyper can have a better name basically. Would love to hear your thoughts @azure osprey !

#

Feel free to react to my messages as you process my feedback, and/or make changes on your posts as you like. I think this doc would get seen by the translator perhaps.

We’d likely need Walt’s opinions around renaming Cabal’s Chinese name too

#

Viktor_ and I made some earlier suggestions on Chinese translations, and a small subset of those translations were seen here again. Not sure if the translator missed them somewhere in the notes.

full sun
#

Circling back to 37, I like that we turned Cabal’s current Chinese translation of “political faction/branch” is suggested to change to “theocracy”. I think Cabal really doesn’t have a Chinese direct translation, and for all intents and purposes theocracy fits well enough there

azure osprey
azure osprey
full sun
full sun
azure osprey
full sun
#

fair fair! your explanation of #30 makes sense to me especially, thanks!

azure osprey
# full sun 39. 泛用性-> 通用性 perhaps? 45. I think titanium steel sounds better/cooler than trit...
  1. OK
  2. Tritanium is the original word. If Walt use Tritanium instead of Titanium, I think there is no reason to change it back.
  3. OK
  4. It's a ship class, distinguishing from asteroids. Another reason is that in other games like StarCraft the word Terran is translated into 人类/人族。
  5. Indeed 脉冲 is actually pulse, but I have no better idea to describe the shots of laser blasters and disruptors. But definitely not 螺栓 !
    (In addition, the abbreviation EMP is so common that even science fiction enthusiasts can understand it even if it is not translated into 电磁脉冲 .)
full sun
#

sounds great! yeah I think keeping EMP missiles as-is is fine too

#

thanks for checking out the feedback! unless someone else wants to chime in too, I think I’m happy with the feedback feedback

azure osprey
#

When will these be ACTUALLY addressed?? @plucky trench I completely ploughed through the language file, spent almost a whole day doing the work that should HAVE BEEN DONE by the paid translator, and then sat back and waited a month without waiting for any of them to be adopted? I wasn't annoyed AT ALL, because I knew Walt was probably struggling with bugfixing, so please just tell me what further information should I provide, representations of these errors in the real game, or a collection of memes based on these errors?

full sun
#

I’ll be following this topic too 👀 But yeah once the concerns by OP are addressed, we’ll have very good Chinese localization

#

Can the translator get discord? I think it can speed up communications if we can chat with them directly, or at the very least they’ll be able to interpret what we write here and fit the fixes in

plucky trench
#

I'll ping the translator again about these fixes. If I don't hear back soon then maybe I can upload the .rules file here and y'all can make the changes while I search for a new translator.

#

I think the translator lives in China and was having some issues accessing Discord. (They were even having trouble downloading through Steam, I had to make them a special non-Steam build.)

#

Or actually you of course already have the .rules file. If someone wants to make the needed edits to it and someone else can review them for accuracy, then I'll use them.

azure osprey
# plucky trench I think the translator lives in China and was having some issues accessing Disco...

Yeah, there are some barriers in Chinese mainland preventing people from accessing foreign websites, but it is not expensive to bypass them if not doing something illegal, especially Steam: there are public, free, and well-known web tools, known as accelerators, that allow users to get access to Steam. (Network acceleration for specific games is still a paid service.) Given how popular Steam is among Chinese single-player game enthusiasts nowadays, I have reason to believe that the translator has never even been exposed to Steam.
Walt, you have said that we all players have a far better understanding of the game than a professional translator will, and we can do a better job. I felt right then, and now I think it's even more right.

full sun
# azure osprey Yeah, there are some barriers in Chinese mainland preventing people from accessi...

I can endorse OP here as a solid translator, though yeah I also think the original translator set some groundworks that have been useful to work from, however misguided/overly transliteral he might’ve been sometimes. Some credit where it’s due haha.

@azure osprey If you’d like to have the changes made in the .rules file later on —let’s give the translator a chance first— then I’ll be happy to review it line-by-line. (I made some minor suggestions earlier, would love to see some of those changes too if they’re agreeable with you!) Ping me when/if we’re ready 😄

azure osprey
full sun
#

@azure osprey Hey man! I think it’s been a solid while, definitely let me know if there are still translations that we can fix/upload, I’d be down to take a look.

Alternately, Walt has made a post here (#translation message) that says we can provide translation suggestions to OneSky. I’m happy to assist with either option. Hope all is well with you!