Crates.io | poreader |
lib.rs | poreader |
version | 1.1.2 |
source | src |
created_at | 2021-12-01 06:26:46.396326 |
updated_at | 2024-05-09 20:33:45.58823 |
description | Read translation catalogs in PO format. |
homepage | |
repository | https://github.com/corebreaker/poreader |
max_upload_size | |
id | 490132 |
size | 188,494 |
poreader
Rust library for reading translation catalogs in Uniforum/Gettext PO. Similar to the translate.storage package in Python Translate Toolkit.
Only PO and Xliff are planned to be supported. For anything else, just convert it with Translate Toolkit. There is no point in replacing that excellent library; the main reason for Rust parser and writer is to them as part of build process of Rust programs, especially in procedural macros, which need to be written in Rust.
On Docs.rs.
It uses Cargo, Rust's package manager. You can depend on this library by adding poreader
to your Cargo dependencies:
[dependencies]
poreader = "1.1"
Or, to use the Git repo directly:
[dependencies.poreader]
git = "https://github.com/corebreaker/poreader.git"
Start by creating a PO reader from a new PO parser, then iterate on the reader:
use poreader::PoParser;
use std::{env::args, fs::File, io::{Result, Error, ErrorKind}};
struct NoArg;
impl std::error::Error for NoArg {}
impl std::fmt::Display for NoArg {
fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result { std::fmt::Debug::fmt(self, f) }
}
impl std::fmt::Debug for NoArg {
fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result { write!(f, "No file specified") }
}
fn main() -> Result<()> {
// Filename
let filename = match args().skip(1).next() {
Some(v) => v,
None => { return Err(Error::new(ErrorKind::Other, NoArg)); }
};
// Open a file
let file = File::open(filename)?;
// Create PO parser
let parser = PoParser::new();
// Create PO reader
let reader = parser.parse(file)?;
// Read PO file by iterating on units
for unit in reader {
let unit = unit?;
// Show `msgid`
println!(" - {}", unit.message().get_id())
}
Ok(())
}
The project works for instance.
Future changes is directely related to the change of the format of the PO file.
However, it would be updated with a need from contributors. You can post an issue or a pull request if you see something that can be improved.