How PHP implements unified text rendering for platform expansion

The requirement is this, in order to achieve a unified format and style of two platform text, to the previous HTML code shaving, because the other platform can not parse the HTML, can only re-set the protocol of the other platform. There is no unified way to solve this problem, I think in the definition of a unified template engine to parse, but for the complex HTML does not seem to have a common approach.

Example code:
Web-side: [♂]$name
Other platforms: $name to implement the above code might be like this

Can realize unification both.

With a set of databases, we now have two options to redefine the template engine but it doesn't seem to be universal. Or the database adds a field to the same $name, stores two copies, reads the time according to the different platform to take out.

There's a better way.

Reply content:

The requirement is this, in order to achieve a unified format and style of two platform text, to the previous HTML code shaving, because the other platform can not parse the HTML, can only re-set the protocol of the other platform. There is no unified way to solve this problem, I think in the definition of a unified template engine to parse, but for the complex HTML does not seem to have a common approach.

Example code:
Web-side: [♂]$name
Other platforms: $name to implement the above code might be like this

Can realize unification both.

With a set of databases, we now have two options to redefine the template engine but it doesn't seem to be universal. Or the database adds a field to the same $name, stores two copies, reads the time according to the different platform to take out.

There's a better way.

Develop a functional module dedicated to parsing.

