Nodeum Docs
HomepageBlog
  • ✨What is Nodeum?
    • Data Management Software
  • 👣GETTING STARTED
    • Step by Step
  • 🏨ARCHITECTURE
    • Standalone
    • High Availability
    • Fully Scalable & Resilience
  • Install and Deploy Nodeum
    • Platform Support
    • Nodeum v1
      • Ansible based installation
    • Nodeum v2 - Data Mover
      • Ansible based Installation
        • Customize your Installation
      • Docker Based Deployment
    • SLURM Integration
    • Software License Application
  • Interfaces
    • ND Client
    • Console
      • Manual for Administrator
        • Login
        • Dashboard & Reports
        • Catalog
        • Data Mover Management
        • Advanced Task Management
        • Data Container
        • Primary Storage Configuration
        • Pool Management
        • TCO Calculator
        • Toolbox
        • System Settings
          • Information
          • Configuration
          • Date & Time
          • Backup
          • Services
          • Hostname and DNS Configuration
          • NAS Storage Configuration
          • Object Storage Configuration
          • Tape Library Configuration
          • User Management
          • Audits
      • Manual for End User
    • For Developers
      • RESTful API
      • Configuration through RestAPI Console
      • Software Developement Kits (SDK)
      • Nodeum API
        • API Terms of Use
        • release v1.x
        • release v2.x
  • DATA MOVER
    • Policy-Based Task orchestration
      • Pool Management
      • Scheduler
      • Data Integrity
      • Priority Management
      • Filtering (Basic or Advanced)
      • Hook service (callback)
    • Content traceability
    • Metadata Management
  • IDENTITY MANAGEMENT
    • Right - Authentication & Authorization
    • LDAP Plugin for JWT Token
  • Container Configuration
    • Prerequisites
    • About Container
    • Authorization and Authentication
    • Access your Container
  • HYBRID STORAGE MANAGEMENT
    • File System Managment
    • Object Storage Management
      • Customize your S3 connection
    • Tape Library Management
      • Tape Writing Format : LTFS
      • Tape Compression
      • Tape Rehydratation
      • Import a LTFS Tape
      • Task Maintenance for Tapes
  • ⏰Alert & Monitoring
    • Alerts
    • Monitoring
    • Log Management
  • 🏥Recover after Hardware Failure
    • Failover - Active/Passive
    • Failover Procedure - One Site
    • Backup & Restore
  • 🔐Security Guide
    • Advanced Network Configuration
    • Add a SSL Certificate on Web Console
    • Enable SSL Certificate Container accessible on S3 Protocol
  • Compatibility guide
    • Software requirement
    • Supported Storage
  • PRODUCT SPECIFICATIONS
    • Character Set Support
    • Limitations
    • Files Status
    • Task Status
Powered by GitBook
On this page

Was this helpful?

  1. PRODUCT SPECIFICATIONS

Character Set Support

All character data is encoded using UTF-8, ensuring consistent representation across containers, primary storage, and secondary storage systems.

UTF-8 is a variable-length encoding standard defined by RFC 3629, capable of representing all 1,112,064 valid Unicode code points using one to four 8-bit bytes:

  • Code points in the ASCII range (U+0000 to U+007F) are encoded using a single byte, maintaining direct binary compatibility with ASCII.

  • Code points in higher ranges are encoded using two to four bytes, with a structure designed to minimize size for commonly used characters and maximize compatibility.

This encoding strategy ensures full Unicode support, efficient storage, and reliable interoperability with modern file systems and network protocols.

UTF-8 Restrictions

Certain UTF-8 characters are restricted when used in file or folder names:

  • The characters / and | are not permitted in file or folder names, as they are reserved by the filesystem and shell.

  • The characters % and : cannot be used as the sole character in a file or folder name.

If a file or folder is encoded using a non-UTF-8 character set, it will be automatically re-encoded using the pattern: %MNGA182 followed by the hexadecimal representation of the original name. This ensures compatibility and traceability of files with unsupported or legacy encodings.

Last updated 28 days ago

Was this helpful?