alfsb

Results 106 comments of alfsb

> No, relying on code in `doc-base` from `web-doc` using a git submodule is a hard pass for me. The inverse. Having code from `doc-base` into `web-doc` as a submodule....

Accidentally closed when cleaning up my fork, to first start working on code duplication of `revcheck.php`, in a bug compatible manner. I will wait the code de-duplication before tackling the...

An fix for issue two (sequential [skip-revcheck] marks files outdated in translations) was proposed in PR 178. A solution for issue one (squashed commits doesn't mark files outdated) are in...

> Initial support for generic sentences via PI instead of forcing translations (and English docs) to write the same thing over and over again, also improves consistency. Some overall ideas,...

Going for simple cases, without fixing any syntax could be like: ```xml ``` On `en/entities/pi/gen_error_section_value_error_between.php`: ```php $PI["gen_error_section_value_error_between"] = function( DOMProcessingInstruction $pi ) { $args = explode( trim( $pi->value ) ,...

Alternative, for (most of) simple cases. On `en/entities/gen_error_section_value_error_between.php`: ```php $PI["gen_error_section_value_error_between"] = function( DOMProcessingInstruction $pi ) { $args = "PARAMETER MIN MAX"; $text =

> I don't really understand what benefit there is in forcing translations to deal with the functions that handle the PI nodes. I can think of two benefits. First, this...

> I don't really understand what benefit there is in forcing translations to deal with the functions that handle the PI nodes With support on `configure.php` to treat PI's return...

> Yeah, but will we ever need this generality? Can't we keep it simpler. I mean, all we need are printf style strings; these can be stored in INI files...

Hi @codingwithrk . I will try to give specific instructions for starting a new manual language. This is not an official instruction, but may be a base for future documentation....